Slack

Message your Chief of Staff from one Slack direct message, using your own private Slack app in Socket Mode.

At a glance

Pair a private Slack app with your Chief of Staff and you can message your Chief from a Slack direct message. Write to it in text and it answers there, including with voice notes. Approvals come as buttons in the same message, or 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.

Takes about 10 minutes at the computer running Murage

You need

A Slack workspace where you can create and install apps
A Chief of Staff in your workspace

Set up Slack

Do the five steps in order. Each one ends with a green box that tells you it worked.

Step 1

Create a private Slack app

In SettingsMessaging 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:

Create a new app from scratch in your workspace.
Turn on Socket Mode. Create an app-level token with the connections:write scope. It starts with xapp-.
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.
Under Event Subscriptions, turn events on and subscribe to the message.im bot event.
In App Home, allow people to send messages to the app from the Messages tab, so you can DM it.
Install the app to your workspace and copy the bot token. It starts with xoxb-.

You're done when: you have copied the bot token that starts xoxb- and the app-level token that starts xapp-.

Step 2

Save the credentials in Murage

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.
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."

The Slack card in Messaging apps with empty token fields — Paste the two tokens here.

You're done when: you see Credentials saved. Pairing has not started.

Step 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.

You're done when: you chose Save workspace details.

Step 4

Pair with your Chief

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

The status reads Waiting for your Slack message, then Connected to Chief.

You're done when: the status reads Connected to Chief and your Chief answers in the DM.

Step 5

Link the account to yourself

The first reply asks you to link this account before chatting.

Open Team map and choose Manage memory.
Under People and verified accounts, find the "Slack account" row.
Choose This is my account.

Then send your message again.

You're done when: you chose This is my account and your resent message gets an answer.

What works

Text: message your Chief in the DM and it answers there.
Voice: ask your Chief for a voice note and it sends one here. Your Chief reads text messages, not voice messages or files. 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

In a direct message with your Chief, an approval request arrives with Slack buttons: Approve once and Deny. Computer-control requests show Deny only and are approved in the desktop app. Typing "approve", "yes" or /approve never approves anything, and you'll get:

Review approvals in Murage. Slack messages cannot approve actions.

You can also answer requests in the app, the Inbox, the menu bar or Telegram.

If your Chief's default is Full access or No limits, your own direct messages run at that level, without cards. The switch is Also skip approvals for my messages from Telegram, Slack and Discord in Bot settingsPermissions. It's on unless you turn it off.

Limits

One of each. One Slack app, one direct message, one owner, your Chief only.
Long replies. Replies longer than 4,000 characters are cut short. Read the full result in Murage.
Three tasks at a time. Up to three unfinished tasks from Slack at a time.
Retries. 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

Find the message you see, then do what the right column says.

You see

Save your Slack credentials

Do this

One or both tokens are missing. Both are needed before pairing.

You see

Pairing code expired

Do this

Also shown as "The code expired. Revoke the incomplete connection, then create a new pairing code." Choose Revoke connection, then Pair with Chief again.

You see

Pairing could not start. Check that a Chief is selected...

Do this

Check both tokens and the three IDs are saved, and revoke any half-finished connection first.

You see

The credentials do not match the saved app identity.

Do this

The tokens belong to a different app or workspace than the IDs. Revoke, fix the details, and pair again.

You see

Your Chief changed. Revoke this connection, then pair with the current Chief.

Do this

Do exactly that.

You see

Automatic reconnect attempts stopped.

Do this

After several failed reconnects Murage stops trying. Check your internet and the app's access, then choose Retry connection.

You see

Pairing saved · receiver offline

Do this

The pairing is kept but Murage isn't listening. Choose Refresh status, then Retry connection if it appears.

You see

Secure storage is unavailable in this window.

Do this

Save credentials from the Murage desktop app, not a browser.

You see

A reply delivery is uncertain. Check Slack before sending the message again.

Do this

Look in Slack before repeating the request.

You see

No reply at all

Do this

Check the computer is awake, Murage is running, the message.im event is on and you're messaging from the owner account.

Slack

Message your Chief of Staff from one Slack direct message, using your own private Slack app in Socket Mode.

At a glance

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.

Takes about 10 minutes at the computer running Murage

You need

A Slack workspace where you can create and install apps
A Chief of Staff in your workspace

Set up Slack

Do the five steps in order. Each one ends with a green box that tells you it worked.

Step 1

Create a private Slack app

In SettingsMessaging 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:

Create a new app from scratch in your workspace.
Turn on Socket Mode. Create an app-level token with the connections:write scope. It starts with xapp-.
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.
Under Event Subscriptions, turn events on and subscribe to the message.im bot event.
In App Home, allow people to send messages to the app from the Messages tab, so you can DM it.
Install the app to your workspace and copy the bot token. It starts with xoxb-.

You're done when: you have copied the bot token that starts xoxb- and the app-level token that starts xapp-.

Step 2

Save the credentials in Murage

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.
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."

You're done when: you see Credentials saved. Pairing has not started.

Step 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.

You're done when: you chose Save workspace details.

Step 4

Pair with your Chief

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

The status reads Waiting for your Slack message, then Connected to Chief.

You're done when: the status reads Connected to Chief and your Chief answers in the DM.

Step 5

Link the account to yourself

The first reply asks you to link this account before chatting.

Open Team map and choose Manage memory.
Under People and verified accounts, find the "Slack account" row.
Choose This is my account.

Then send your message again.

You're done when: you chose This is my account and your resent message gets an answer.

What works

Text: message your Chief in the DM and it answers there.
Voice: ask your Chief for a voice note and it sends one here. Your Chief reads text messages, not voice messages or files. 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

Review approvals in Murage. Slack messages cannot approve actions.

You can also answer requests in the app, the Inbox, the menu bar or Telegram.

Limits

One of each. One Slack app, one direct message, one owner, your Chief only.
Long replies. Replies longer than 4,000 characters are cut short. Read the full result in Murage.
Three tasks at a time. Up to three unfinished tasks from Slack at a time.
Retries. 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

Find the message you see, then do what the right column says.

You see

Save your Slack credentials

Do this

One or both tokens are missing. Both are needed before pairing.

You see

Pairing code expired

Do this

Also shown as "The code expired. Revoke the incomplete connection, then create a new pairing code." Choose Revoke connection, then Pair with Chief again.

You see

Pairing could not start. Check that a Chief is selected...

Do this

Check both tokens and the three IDs are saved, and revoke any half-finished connection first.

You see

The credentials do not match the saved app identity.

Do this

The tokens belong to a different app or workspace than the IDs. Revoke, fix the details, and pair again.

You see

Your Chief changed. Revoke this connection, then pair with the current Chief.

Do this

Do exactly that.

You see

Automatic reconnect attempts stopped.

Do this

After several failed reconnects Murage stops trying. Check your internet and the app's access, then choose Retry connection.

You see

Pairing saved · receiver offline

Do this

The pairing is kept but Murage isn't listening. Choose Refresh status, then Retry connection if it appears.

You see

Secure storage is unavailable in this window.

Do this

Save credentials from the Murage desktop app, not a browser.

You see

A reply delivery is uncertain. Check Slack before sending the message again.

Do this

Look in Slack before repeating the request.

You see

No reply at all

Do this

Check the computer is awake, Murage is running, the message.im event is on and you're messaging from the owner account.

Set up Slack#

Create a private Slack app#

Save the credentials in Murage

Choose your workspace and owner

Pair with your Chief

Link the account to yourself

What works

Approvals

Limits

Change or remove it

Troubleshooting

Search murage.ai

Set up Slack#

Create a private Slack app#

Save the credentials in Murage

Choose your workspace and owner

Pair with your Chief

Link the account to yourself

What works

Approvals

Limits

Change or remove it

Troubleshooting

Set up Slack

Create a private Slack app

Set up Slack

Create a private Slack app