Slack

Pair a private Slack app with your Chief of Staff and you can message your Chief from a Slack direct message. It answers there, including with voice notes. Approvals stay in Murage: answer them in the app, the Inbox, the menu bar or Telegram.

Murage must be running on your computer to receive messages. It connects to Slack from your computer using Socket Mode, so you don't need a public web address.

This is different from Slack as a connected app, where bots read and post in your workspace as a tool.

What you need#

• A Slack workspace where you can create and install apps.
• About ten minutes at the computer running Murage.
• A Chief of Staff in your workspace.

1. Create a private Slack app#

In Settings → Messaging apps, the Slack card has a Private Slack app setup section with the exact requirements, and Open Slack app settings takes you to Slack's app page. On Slack's side:

1. Create a new app from scratch in your workspace.
2. Turn on Socket Mode. Create an app-level token with the connections:write scope. It starts with xapp-.
3. Under OAuth scopes, add these bot token scopes: im:history and chat:write. Add files:write too if you want voice notes sent to Slack.
4. Under Event Subscriptions, turn events on and subscribe to the message.im bot event.
5. In App Home, allow people to send messages to the app from the Messages tab, so you can DM it.
6. Install the app to your workspace and copy the bot token. It starts with xoxb-.

Keep the app private to your workspace.

2. Save the credentials in Murage#

1. In the Slack card, under 1. Save credentials securely, paste the app-level token into App-level token and the bot token into Bot token.
2. Choose Save credentials.

Both are stored encrypted on your computer and never shown again. Leave a field blank later to keep the saved key. You'll see "Credentials saved. Pairing has not started."

3. Choose your workspace and owner#

Under 2. Choose your workspace and owner, fill in three IDs:

• Workspace ID: your Slack workspace's ID. It starts with T.
• App ID: from your app's Basic Information page. It starts with A.
• Owner member ID: your own Slack member ID, from your profile (Copy member ID). It starts with U.

Choose Save workspace details. Only this owner can pair and send messages to your Chief.

4. Pair with your Chief

1. Under 3. Pair with Chief, choose Pair with Chief.
2. Murage shows a message: pair followed by a long code. Choose Copy pairing message.
3. In Slack, open a direct message with your app, as the owner above, and send the message.

The code expires after 10 minutes. The status reads Waiting for your Slack message, then Connected to Chief.

5. Link the account to yourself

The first reply asks you to link this account before chatting. Open Team map, choose Manage memory, find the "Slack account" row under People and verified accounts, and choose This is my account. Then send your message again.

What works

• Text: message your Chief in the DM and it answers there.
• Voice: send your Chief a voice message and it replies with a voice message. Voice notes need the files:write scope, plus Flux Router credits or your own voice keys.
• Pictures and files: share these in Murage. The Slack DM is for talking to your Chief.

Only the owner's direct messages are read. Channels, other people's messages, bot messages and shared (Slack Connect) conversations are ignored.

A reply comes back to Slack only for a message you sent from Slack. Work you start in Murage, and routines, report in the app.

Approvals stay in Murage

Slack doesn't approve anything. If you type "approve", "yes" or /approve, you'll get "Review approvals in Murage. Slack messages cannot approve actions." Answer requests in the app, the Inbox, the menu bar or Telegram.

If your Chief's default is Full access or No limits, Bot settings → Permissions has Also skip approvals for my messages from Telegram, Slack and Discord.

Limits

• One Slack app, one direct message, one owner, your Chief only.
• Replies longer than 4,000 characters are cut short. Read the full result in Murage.
• Up to three unfinished tasks from Slack at a time.
• Murage retries a failed reply a few times, then asks you to review it rather than send it twice.

Change or remove it

Choose Revoke connection to stop. Your saved credentials stay. You need to revoke before changing credentials, the workspace details or the owner.

Troubleshooting

• "Save your Slack credentials": one or both tokens are missing. Both are needed before pairing.
• "Pairing code expired" or "The code expired. Revoke the incomplete connection, then create a new pairing code.": choose Revoke connection, then Pair with Chief again.
• "Pairing could not start. Check that a Chief is selected...": check both tokens and the three IDs are saved, and revoke any half-finished connection first.
• "The credentials do not match the saved app identity.": the tokens belong to a different app or workspace than the IDs. Revoke, fix the details, and pair again.
• "Your Chief changed. Revoke this connection, then pair with the current Chief.": do exactly that.
• "Automatic reconnect attempts stopped.": after several failed reconnects Murage stops trying. Check your internet and the app's access, then choose Retry connection.
• "Pairing saved · receiver offline": the pairing is kept but Murage isn't listening. Choose Refresh status, then Retry connection if it appears.
• "Secure storage is unavailable in this window.": save credentials from the Murage desktop app, not a browser.
• "A reply delivery is uncertain. Check Slack before sending the message again.": look in Slack before repeating the request.
• No reply at all: check the computer is awake, Murage is running, the message.im event is on and you're messaging from the owner account.

Related: Channels overview, Channels guide, Phone and chat, Voice notes.