Connect a Slack app to any Friday workspace so users can chat with it over DM orDocumentation Index
Fetch the complete documentation index at: https://docs.hellofriday.ai/llms.txt
Use this file to discover all available pages before exploring further.
@mentions. Messages flow into the same conversation pipeline the web chat uses, and replies go back to Slack.
Prerequisites
- A Slack workspace where you can install apps (admin, or one that allows member-installed apps).
- Friday running with the bundled tunnel active (Slack requires a public HTTPS URL).
Setup
Grab your tunnel URL
Open Studio → Settings → Webhook tunnel and copy the URL — something like
https://<random>.trycloudflare.com. Keep it handy for the next step.Create the Slack app from a manifest
- Open api.slack.com/apps and click Create New App → From a manifest.
- Pick the Slack workspace you want to install into.
-
Paste the manifest below, replacing
<your-tunnel>with the tunnel host from the previous step: - Click Next → Create. Slack provisions scopes, event subscriptions, and the App Home messages tab from the manifest.
Install the app and copy three values
- Go to OAuth & Permissions and click Install to Workspace. Approve the OAuth prompt.
- From the app dashboard, copy:
- App ID — under Basic Information → App Credentials
- Signing Secret — same section, click Show to reveal
- Bot User OAuth Token — starts with
xoxb-…, under OAuth & Permissions
Connect Slack in Studio
- Open Studio and pick your workspace.
- Find the Communicators card and click Connect next to Slack.
- Paste the App ID, Signing Secret, and Bot Token into the form, then submit.
Verify the Request URL
Back in Slack’s Event Subscriptions, the Request URL should report Verified once Friday is running. If it shows a yellow banner, click Retry.
Talk to your bot
- In Slack, find the app under Apps in the sidebar, or DM it by name.
- Send a message. The first message creates a chat in the workspace — it should appear in Studio with a blue SLACK badge, and replies flow back to Slack automatically.
- To talk to the bot in a channel, invite it first (
/invite @bot-name), then@bot-name hello.
Troubleshooting
Slack shows 'Your URL didn't respond' during verification
Slack shows 'Your URL didn't respond' during verification
Check that the tunnel is running — Studio → Settings → Webhook tunnel should show active with a URL. If the tunnel just restarted, Cloudflare assigns a new URL — paste the fresh one into the manifest’s
request_url.Request URL verifies, but messages don't trigger anything
Request URL verifies, but messages don't trigger anything
Double-check that you connected Slack in Studio for this workspace, and that the App ID you pasted matches the one in Slack’s Basic Information.
Signature verification fails
Signature verification fails
The Signing Secret you pasted doesn’t match the current one. In the Slack app dashboard click Show under Signing Secret, copy fresh, and reconnect via Studio.
Bot doesn't respond to @mentions in channels
Bot doesn't respond to @mentions in channels
Invite the bot to the channel first (
/invite @bot-name).Configure via YAML
Skip Studio and configure from disk
Skip Studio and configure from disk
For CI or fully scripted setups, paste credentials directly into Save and restart Friday. You’ll still need to set Slack’s Request URL to
workspace.yml or the .env file in the Friday home directory (default ~/.atlas/.env). app_id is always required.- Credentials inline
- Credentials via env
workspace.yml
<tunnel>/platform/slack and subscribe to message.im and app_mention events — the manifest above does this in one shot.
