Uses: Python · TypeScript · CLI
1. Connect Slack
Steps 1-2 are one-time setup, shown in the CLI because its guided flow is the fastest path - the connection it creates is immediately usable from both SDKs (and step 3 does the same discovery in SDK code):2. Find the tools you actually have
Tool slugs vary by connector version, so discover rather than assume:3. Scope a toolset
Give the agent only what it needs. An assistant that should never delete anything simply isn’t handed a delete tool:4. The agent loop
Identical to the monday assistant - the loop is app-agnostic:Posting without an LLM
Plenty of “Slack agents” don’t need a model at all - a scheduled job that posts a digest is just a tool call:Where to take it next
- Scope it harder - toolsets make “read-only in #support” an API-enforced guarantee rather than a prompt instruction
- Add a second app - bind two connections in one toolset and the agent can read Slack and file a ticket in the same turn
- Handle failures - a Slack rate limit surfaces as
isSuccess: falsewith the downstream status inexecutionInfo; see debugging