Connect Slack

≈ 3 min Extension Bearer Token

Before you start

• A Slack workspace where you may install apps (or an admin who approves it).
• The AWFlow browser extension. These steps run in the extension (the web app hands them to it).

Used by

• Slack

Pick a method

Method	Use it when
Bot token Recommended	Posts as your app. Covers every operation except Message › Search.
User token	Acts as you. Needed for Message › Search; it also sees every channel you are in.

Set it up

Bot token (recommended)

1. Create the app from a manifest. Open api.slack.com/apps, click Create New App › From a manifest, pick your workspace and paste:

   awflow-slack-manifest.yaml

   display_information:
     name: AWFlow
   features:
     bot_user:
       display_name: AWFlow
       always_online: false
   oauth_config:
     scopes:
       bot:
         - channels:read
         - groups:read
         - channels:history
         - groups:history
         - chat:write
         - users:read
         - files:read
         - files:write
       user:
         - search:read
   settings:
     org_deploy_enabled: false
     socket_mode_enabled: false
     token_rotation_enabled: false

   Drop the scopes you won’t use. The user scope is only for Message › Search.

2. Install it and copy the token. Click Install to Workspace and allow. In OAuth & Permissions, copy the Bot User OAuth Token (it starts with xoxb-).

3. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Slack in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Slack Under Integration App / Service, pick Slack. There is no Auth Type menu: Slack uses a Bearer Token.
   2. 2 Step 2:Name it For example Slack – AWFlow bot. A Description is optional.
   3. 3 Step 3:Paste the token Paste the xoxb- token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Slack; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

4. Invite the bot to each channel it should post in or read: type /invite @AWFlow in the channel.

Check it's connected — 

In a Slack node, pick the credential: the Channel list fills with your channels. Then run Channel › Get many with Test step.

User token

1. Use the same app (the manifest above already asks for search:read as a user scope), or add User Token Scopes under OAuth & Permissions.

2. Reinstall the app to the workspace, then copy the User OAuth Token (it starts with xoxp-).

3. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap Slack in the list, then fill the rest.

   12345

   1. 1 Step 1:Pick Slack Under Integration App / Service, pick Slack. There is no Auth Type menu: Slack uses a Bearer Token.
   2. 2 Step 2:Name it For example Slack – me (search). A Description is optional.
   3. 3 Step 3:Paste the token Paste the xoxp- token into Bearer Token.
   4. 4 Step 4:Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Step 5:Click Create Credential Check: the credential is listed on the Credentials page, ready to pick in nodes.

   Numbered areas in the screenshot: 1. Integration App / Service: Slack; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Message › Search with a word you know is in a channel: matching messages come back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to slack.com and files.slack.com. AWFlow’s servers never relay the call.

Privacy & your data →

Permissions each operation needs

Operation	Token	Scope
Channel · Get many, Get info	Bot or user	channels:read (groups:read for private channels)
Message · Send, Update, Delete	Bot or user	chat:write
Message · Get	Bot or user	channels:history (groups:history for private channels)
Message · Search	User only	search:read
User · Get many, Get info	Bot or user	users:read
File · Upload	Bot or user	files:write
File · Get	Bot or user	files:read

Common issues

• “missing_scope” or “not_allowed_token_type”. The token lacks the scope for this operation, or Search got a bot token. Add the scope in your Slack app, reinstall it, and copy the new token.
• “not_in_channel”. Invite the bot to the channel with /invite @AWFlow.
• “invalid_auth”. The token was revoked or the app was reinstalled. Copy the current token from OAuth & Permissions.
• The Channel list stays empty. Pick the credential first; the list loads from Slack with it.
• The run is blocked in the web app. Slack runs through the browser extension. Install the extension and allow Slack for this workflow when asked, or run the workflow from the extension. See Extension-only integrations in the web app.

Related

Slack node

All connections

Create and manage credentials

Privacy & your data