Slack
Install Jaah in your Slack workspace: questions, task updates and replies in Slack.
Connect it with: Sign in (OAuth). Slack's own documentation: https://docs.slack.dev/authentication/installing-with-oauth.
What agents can do
Connect Slack so the agents working your tasks can reach it. With it connected, they can:
- Ask a person a question in Slack when a task needs a human answer, and carry the reply back to the task.
- Post task updates and results to the channel you choose.
- Start or answer work when someone mentions @Jaah.
- Show a preview card under Jaah task links pasted in Slack.
Before you start
- Permission to install apps in the Slack workspace (a Workspace Owner or Admin, or a member where the workspace lets members install apps).
- A Jaah plan that includes Slack, and the Jaah Owner or Admin role in your org.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Slack
This is the quickest way in: you sign in to Slack and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for Slack and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect Slack. Slack's sign-in window opens.
- Sign in to Slack if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at Slack yet. Use your own OAuth app until it does (see Use your own OAuth app).
Scopes Jaah requests
Jaah asks Slack for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
chat:write | Post task questions, updates and results in channels Jaah is in | Yes |
im:write | Open a direct message with a person to ask them a question | Yes |
im:history | Read replies in those direct messages, so an answer reaches the task | Yes |
app_mentions:read | See when someone mentions @Jaah, to start or answer a task | Yes |
links:read | See Jaah links posted in Slack, to unfurl them | Yes |
links:write | Show a preview of a Jaah task under its link | Yes |
users:read | Match Slack members to Jaah members, so the right person is asked | Yes |
channels:read | List the public channels, so an Owner or Admin can pick one for alerts | Yes |
groups:read | List the private channels Jaah was invited to, for the same choice | Yes |
chat:write.public | Post alerts in a public channel Jaah was not invited to | Yes |
Connect with an API key
Slack has no API key option in Jaah: connect with the sign-in above.
Use your own OAuth app
Register your own OAuth app at Slack when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in Slack's developer settings (Slack's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new Slack secret, select Use your own OAuth app, paste both values and select Connect Slack.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Slack with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
Tell the agent in your task description which secret to use, for example “use the Slack secret org/slack”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Reconnect: when Slack ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Slack's side too, revoke Jaah in Slack's settings.
Limitations
- One Slack workspace per Jaah org. Connecting another workspace replaces the first.
- Jaah only sees channels it is invited to: type /invite @Jaah in a channel to add it.
- The Slack install is the org's: its bot token is held by Jaah for messaging and is never handed to agents.
- Enterprise Grid orgs install per workspace, and an org admin may need to approve the app first.
- Agents can do only what the connected Slack account and its granted scopes allow.
Troubleshooting
Slack says the app is not approved or requires admin approval
Your workspace restricts app installs. Ask a Slack admin to approve Jaah (Slack admin > Manage apps), then select Connect Slack again.
Jaah does not answer in a channel
Jaah is not in that channel. Type /invite @Jaah in it.
Add channel says Reconnect Slack in Settings to add channels
Your workspace was connected before Jaah could list channels. An Owner or Admin selects Reconnect on the org's Slack tab and approves the app again.
Test says Slack rejected the bot token (invalid_auth or token_revoked)
Jaah was uninstalled from the workspace. Select Connect Slack again to reinstall it.
Still stuck? Select Test and read the result: it names the value Slack refused and the status it answered.
FAQ
Do I need my own Slack app?
No. Connect Slack installs Jaah's own Slack app in your workspace.
Can agents read my Slack channels?
No. The install lets Jaah post, read replies to its own direct messages and mentions of @Jaah; it does not read channel history, and the token never reaches an agent.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Slack account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.