WORKFLOW · SLACK WORKFLOWS
Work from
Slack.
Mention @Agent in a Slack thread. It picks up your task, runs, and posts results back. Artifacts, approvals, and status all in Slack. No tab-switching.
@Agent Review the file Dave just posted for security issues
- Slack thread with results
- Approval cards in Slack
- Artifacts linked in Slack
UseAgentExample workflow@Agent Review the file Dave just posted for security issues
Agent picked up mention
Read Slack thread. Found attached file: secrets-config.json. Downloaded it.
Security scan
Found 3 hardcoded API keys in the config. Flagged immediately in Slack thread with severity.
Asked for approval
Before removing, posted approval request: 'Redact these 3 keys and rotate them?' User approved in Slack.
Completed and reported
Posted summary to Slack thread: 3 keys found, redacted, new rotated keys in DM to Dave (not in Slack).
TOOLS IT REACHES
THE RESULT
Issue found and remediated. All in Slack thread.
Questions, answered.
What if I want to use a specific engine?
Reply with engine: '@Agent use claude: analyze this PR'. Default is the org engine setting.
Can the agent access files posted in Slack?
Yes. It downloads attachments, reads them, and works with them. Files are scanned for safety before use.
Do I need to approve every operation from Slack?
Approval gates still apply. Approval cards post to the Slack thread. Approve right there, agent resumes.
Start with one task.
See what you can hand off.
Explore a completed run, or join the early-access list to hear about getting your team started.