Communication
Give your agents full access to Slack.
Agents read channels, follow threads, search history, and post where your team already works. Slack message events let an agent answer the moment a question lands, and channel filters on triggers keep each agent scoped to the conversations that matter.
5,000 free credits to start.
Agent reach
Slack Web API
The full surface, searched at run time.
Connect with
- Helios OAuth app
- Your own OAuth app
Each person authorizes once after the workspace installs the app.
Event triggers
Yes · 2 events
Plus manual, schedule, and signed webhook.
What the agent can do
What agents do with Slack
Helios searches the Slack Web API at run time. The agent finds the endpoint the task needs and calls it.
- Search Slack's entire API surface at run time and call any endpoint within your scopes.
- Read channel history and thread replies, including files and attachments.
- Post messages, thread replies, and rich blocks; update or delete what the agent posted.
- Search across the workspace to reconstruct what happened and who said it.
- React with emoji, pin messages, and manage channel membership.
- Trigger on new messages with a channel filter, so one agent watches one room.
Examples
Tasks you can hand to a Slack agent
Answer support questions in channel
An agent watches your support channel, searches your docs and past threads, and replies with a real answer plus a link.
Watch #support. When someone asks a question, answer it from our docs and past threads.
- slack·read the thread in #support
- notion·search internal help center
- slack·search prior threads for the same question
- slack·reply in thread
Replied in thread
- Answered the SSO group-mapping question
- Linked to the SCIM setup doc
- Tagged @ops because the customer is on Enterprise
Summarize a busy channel
A scheduled agent reads everything that happened, separates decisions from chatter, and posts a digest with open questions called out.
Every evening, summarize #product: decisions made, open questions, who owns what.
- slack·read 24h of #product history
- slack·expand threads with 3+ replies
- slack·post digest to #product-digest
#product · Mar 5
- 3 decisions, including shipping the export beta on Friday
- 2 open questions awaiting @dana
- 1 escalation moved to #incidents
Route escalations to the right owner
The agent recognizes an escalation, pulls the customer record, and pages the owner with everything they need in one message.
When a message looks like an escalation, look up the account and page the owner.
- slack·read message and thread context
- attio·look up the account record
- stripe·check plan and payment status
- slack·DM the account owner with context
Escalation routed
- Account: Northwind · Growth plan · $4.2k MRR
- Owner @priya paged with the thread link
- Follow-up task created in Attio
Broadcast what shipped
When a release publishes, the agent turns the notes into a message your whole company can read and posts it.
When we publish a release, announce it in #general in plain language.
- github·read release v2.8.0 notes
- slack·post announcement to #general
Announced v2.8.0
- Highlighted scheduled exports and the faster search
- Linked the changelog and the upgrade note
Run a standup without the meeting
The agent reads yesterday's commits and merged work, drafts a standup per person, and posts it before the day starts.
Every weekday at 9am, post a standup from yesterday's GitHub activity.
- github·list commits and merged PRs since yesterday
- github·list PRs still awaiting review
- slack·post standup to #standup
Standup · Mar 6
- 5 engineers shipped 12 PRs
- @sam blocked on a review for #2841
- Nothing red in CI overnight
Event triggers
Start a run on Slack events
Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too.
| Event | What it means |
|---|---|
message.channel | A new message lands in a public channel. Filter by channel so one agent watches one room. |
message.group | A new message lands in a private channel the connection has joined, with the same channel filters. |
Works with
Slack works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
Templates
Ready-to-run Slack workflows
Copy the prompt, connect your tools, and start a run.
Support
Slack support triage
Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.
Support
Plain thread triage
Triages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.
Engineering
Pull request reviewer
Reviews every pull request against your conventions and leaves inline comments only where it found something concrete.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.
Engineering
Standup without the meeting
Reads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.
Engineering
Incident postmortem drafter
Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.
Sales & RevOps
Failed payment recovery
Finds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.
Sales & RevOps
Churn risk watchlist
Joins billing signals with product usage and support volume to find the accounts drifting toward the exit.
Sales & RevOps
Inbound lead enrichment
Enriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.
Sales & RevOps
Nightly CRM hygiene
Merges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.
Operations
Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.
Marketing
Reddit brand monitor
Sweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.
Marketing
Research brief writer
Researches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.
Support
Documentation freshness audit
Checks your written docs against the codebase every month and comments on the pages that have gone stale.
Use cases
Where Slack agents fit
Support
Support triage
A workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.
Sales & RevOps
Lead enrichment
A signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.
Engineering
Pull request review
A workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.
Engineering
Incident summaries
A workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.
Operations
Database reporting
A workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.
Marketing
Research briefs
A workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.
Marketing
Community monitoring
A workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.
FAQ
Questions, answered
Put an agent on Slack.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.