AI agents for Slack
Team chat where operations actually surface. AGNT connects to Slack so agents can read what happens there, reason about it, and act — with a receipt for every run.
Support First Responder is a ready-made agent that works in Slack — free, and it runs on your machine.
Slack and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Slack. |
|---|---|
| Connects with | One OAuth sign-in |
| AGNT node | slack-api, receive-slack-message |
| Runs when | A message hits a channel |
| Typical build time | Two minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- a message hits a channel
- a keyword or mention fires
- a reaction is added
Agents can…
- post a rich channel message
- DM a teammate
- open a thread with findings
Teams use it for
- pipe agent findings into the room where decisions happen
- route escalations with full context
- daily digests that replace standup theatre
Build it: the Slack workflow
Take the simplest useful version: a message hits a channel in Slack. Instead of a rule firing blindly, an agent reads the item in full, works out whether it matters and what it means, and then decides whether to post a rich channel message. Over a week that turns pipe agent findings into the room where decisions happen from something a person checks into something that reports to a person.
What follows is the whole workflow, not a sketch of it. Slack supplies the event, the agent supplies the reasoning, and the third node does the thing — or deliberately does nothing, which is a recorded outcome rather than a silent one.
{
"id": "6db6bb1b-fc2b-4ae1-a27d-56b8dd421d6a",
"name": "Slack — read, decide, act",
"nodes": [
{
"id": "c847ac6d-50c4-42c5-adfa-9d1423d9a512",
"text": "Watch Slack for activity",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-slack-message",
"icon": "clock",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for incoming Slack messages in a specified channel and trigger the workflow when a new message is received.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "5f7ed458-f941-4b5e-a17a-1af8d94d0d5c",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Slack item and decide whether it warrants action. Explain your reasoning."
},
"description": "Judges the Slack item against criteria you wrote in plain language.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "e0ba1e3a-cb96-40e5-a325-890110a73d92",
"text": "Act in Slack",
"x": 512,
"y": 528,
"isEditing": false,
"type": "slack-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "SEND_MESSAGE"
},
"description": "Runs SEND_MESSAGE on your behalf.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "6531ca36-663a-4bda-a15f-68dcc41a3f7c",
"start": {
"id": "c847ac6d-50c4-42c5-adfa-9d1423d9a512",
"type": "output"
},
"end": {
"id": "5f7ed458-f941-4b5e-a17a-1af8d94d0d5c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "d8eb1a87-9eec-405d-ab54-49f825950346",
"start": {
"id": "5f7ed458-f941-4b5e-a17a-1af8d94d0d5c",
"type": "output"
},
"end": {
"id": "e0ba1e3a-cb96-40e5-a325-890110a73d92",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}
Install Support First Responder — it runs on Slack
Support First Responder is a working agent that uses Slack. Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
Where agent work becomes visible
Slack is usually the first place an agent should report, because a finding nobody sees may as well not exist. The useful pattern is not piping raw events into a channel but posting written conclusions — what happened, why it matters, what the agent did about it — into the room where the decision would be made anyway.
Approvals in the place people already are
Because Slack is where your team already lives, it is the natural home for approval gates. An agent can post what it intends to do with the context attached and wait for a human to accept before acting, which turns oversight into a message rather than another dashboard nobody opens.
Slack node reference
Interact with Slack to perform various operations such as sending messages, uploading files, managing reactions, and more.
What it can do: SEND_MESSAGE REPLY_TO_THREAD GET_CHANNELS GET_USERS UPLOAD_FILE ADD_REACTION
Full Slack API parameter reference
| Parameter | Type | What it does |
|---|---|---|
actionrequired |
string | The action to perform on Slack SEND_MESSAGE · REPLY_TO_THREAD · GET_CHANNELS · GET_USERS · UPLOAD_FILE · ADD_REACTION |
channelId |
string | The ID of the Slack channel only when action is SEND_MESSAGE or REPLY_TO_THREAD or UPLOAD_FILE or ADD_REACTION |
message |
string | The message to send only when action is SEND_MESSAGE or REPLY_TO_THREAD or UPLOAD_FILE |
threadTs |
string | The timestamp of the parent message to reply to (for REPLY_TO_THREAD) or react to (for ADD_REACTION) only when action is REPLY_TO_THREAD or ADD_REACTION |
emoji |
string | The emoji name without colons (e.g., 'thumbsup', 'heart') only when action is ADD_REACTION |
fileName |
string | The name of the file to upload only when action is UPLOAD_FILE |
fileData |
string | The base64-encoded file data to upload only when action is UPLOAD_FILE |
limit |
number | Maximum number of results to return (for GET_CHANNELS and GET_USERS) only when action is GET_CHANNELS or GET_USERS |
Every parameter above is read from the shipped slack-api node, so it cannot drift from the product.
Connect Slack in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect with one OAuth sign-in from AGNT’s vault — tokens are stored encrypted on your machine and never leave it.
- Drop the Slack node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Slack + AGNT — common questions
Can an agent respond to Slack messages?
Yes — a message, mention, keyword or reaction can trigger a run, and the agent can reply in the thread with its findings.
Do I need admin rights to connect Slack?
You need permission to install an app in the workspace. The OAuth token is stored encrypted on your own machine.
Can approvals happen in Slack?
Yes. Approval gates can surface in Slack with full context, and the run resumes when someone signs off.