Channel
Talk to your AI agent from Slack
Mention the bot and it answers in the thread. Connecting Slack does not create a second agent with different rules: an inbound message goes to the same runtime, through the same tool registry, policy engine and approval gate.
What you get
Slack capabilities, under your rules
- ✓ The same runtime, tool registry, policy engine and approval gate as web chat
- ✓ A destructive request stops for approval exactly as it would in web chat
- ✓ The allowed-senders list starts empty, meaning nobody
- ✓ Senders are identified by the platform’s own id, never a display name
- ✓ A channel run carries nobody’s permissions, so anything that needs one is refused
- ✓ A repeated delivery of the same message is recognised and dropped
What you need to connect it
- Bot user OAuth token — starts with xoxb-, from OAuth & Permissions
- Signing secret — from Basic Information; it proves a request came from Slack
- The Request URL Caterfli shows you, pasted into Event Subscriptions
Human approval
Destructive work waits for a person
approval
waiting- Tool
- delete_customers
- Operation
- DELETE
- Runs against
- Production PostgreSQL
- Agent
- Support Agent
Exactly these values
{
"filters": {
"id": 100
}
}
Your decision applies to these values only. If anything about the call changes, it stops for approval again.
Asked for from Slack. Connecting a channel does not create a second agent with different rules.
Connect Slack to your first agent
Connect one system and read the agent Caterfli writes from it. There is a demo connection too, if you would rather look before you wire anything up.