Slack

What it is

A Slack connection lets workflows post messages to channels and, if you configure the signing secret, lets Slack events start a workflow. It authenticates as a Slack app that you create in your own workspace — Honeybase does not run a shared Slack app, so the bot appears under your name and you control its scopes.

The workspace name and URL are filled in automatically once the token is verified; you do not type them.

Before you start

You need permission to install an app in the target workspace. If your workspace requires admin approval for apps, get that in hand before you begin.

Setup fields

These are the fields the guided setup collects — both the Add integration form and the setup card Barry raises in chat. Additional settings live on the connection's settings page once it exists.

Connection settings

Field	Type	Required	Secret	Notes
name	Text	Yes	No	Display name for this connection. This is what you pick from in a workflow node.

Credentials

Field	Type	Required	Secret	Notes
botToken	Password	Yes	Yes	The bot user OAuth token from your Slack app, starting with xoxb-. Found under OAuth and Permissions after you install the app to a workspace.
signingSecret	Password	No	Yes	The app's signing secret, from Basic Information → App Credentials. Only needed to receive events from Slack; sending works without it.

Creating the Slack app

1. Go to api.slack.com/apps and choose Create New App → From scratch. Name it and pick the workspace.
2. Open OAuth & Permissions and add the bot token scopes you need under Scopes → Bot Token Scopes. For posting messages that is chat:write, plus chat:write.public if you want to post to channels the bot has not been invited to.
3. Choose Install to Workspace at the top of the same page and approve the prompt.
4. Copy the Bot User OAuth Token (xoxb-…). That is the botToken.
5. For the signing secret, open Basic Information → App Credentials and copy Signing Secret.

Receiving events

Sending only needs the bot token. To have Slack events reach Honeybase you also need the signing secret — it is how incoming requests are verified as genuinely from Slack. Add it now if you know you will listen for events; you can add it later on the connection's settings page.

Scopes

Add scopes narrowly. A token with chat:write can post as the app; one with broad read scopes can see far more of your workspace than a workflow needs. If you add scopes later, Slack requires you to reinstall the app, which issues a new token — paste the new one into the connection.

Sending to an email address

Choose Email as the Slack node's recipient type and supply an address or an expression. Add the bot scope users:read.email in Slack's OAuth & Permissions page, reinstall the app, update the stored token if it changed, and run Test Connection. Reselect the integration in the node to refresh its capability check. Email remains unavailable until Slack reports that scope. The server checks again at execution and resolves the address through users.lookupByEmail. An unknown or deactivated user fails the node. A rate-limit error includes retry guidance. Channel and user-ID recipients continue to work without the email scope.