Automate Slack + X (Twitter)
Team chat where operations actually surface. The feed where your market thinks out loud. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Competitive Watch already works across Slack and X (Twitter) — free, and it runs on your machine.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Slack into X (Twitter).
When a message hits a channel in Slack…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a keyword or mention fires in Slack…
…an agent can collect engagement metrics in X (Twitter) — after reading the context and deciding it should.
When a reaction is added in Slack…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a mention or keyword appears in X (Twitter)…
…an agent can post a rich channel message in Slack — with the reasoning recorded in the run’s receipt.
When a schedule fires in X (Twitter)…
…an agent can DM a teammate in Slack — with the reasoning recorded in the run’s receipt.
Slack to X (Twitter), in three nodes
The two ends are the slack-api node and the twitter-api node. What makes this different from a zap is the middle node — it forms a view about the Slack item before anything reaches X (Twitter).
{
"id": "a36c2621-018f-4618-ab20-0e67e1c98ab8",
"name": "Slack → X (Twitter)",
"nodes": [
{
"id": "cc141e69-26c7-4fe7-abfb-91c6a54e286e",
"text": "Watch Slack",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-slack-message",
"icon": "connect",
"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": "53d5e85d-85e3-4264-a909-1ce3f57f4414",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Slack item. Decide whether it warrants action in X (Twitter), and explain why."
},
"description": "Decides whether this Slack item warrants anything in X (Twitter).",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "9f2b9071-8c23-49ee-ab1f-42437471b798",
"text": "Act in X (Twitter)",
"x": 512,
"y": 528,
"isEditing": false,
"type": "twitter-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "POST"
},
"description": "Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "ad75bda7-0c21-4f5b-a8b8-94a02dee481e",
"start": {
"id": "cc141e69-26c7-4fe7-abfb-91c6a54e286e",
"type": "output"
},
"end": {
"id": "53d5e85d-85e3-4264-a909-1ce3f57f4414",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "04eb01e3-a240-4e63-a58c-e8c089c377ae",
"start": {
"id": "53d5e85d-85e3-4264-a909-1ce3f57f4414",
"type": "output"
},
"end": {
"id": "9f2b9071-8c23-49ee-ab1f-42437471b798",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Competitive Watch
Competitive Watch already uses both Slack and X (Twitter), so installing it gives you this exact hand-off wired up — connected, editable, and running on your own machine.
Runs on your own machine · See what it does
Build it in AGNT
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Slack takes one OAuth sign-in, X (Twitter) takes one OAuth sign-in.
- Build the three nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in X (Twitter).
Slack and X (Twitter) — common questions
Can I connect Slack to X (Twitter) without writing code?
Yes. Slack connects with one OAuth sign-in and X (Twitter) with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a message hits a channel, post threads and replies” — and the agent handles the rest.
How is this different from a field-mapping Slack to X (Twitter) automation?
Mapping tools move data; this reasons about it. Rather than copying a field into X (Twitter), the agent can weigh what arrived from Slack, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Slack and X (Twitter) data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Slack, X (Twitter), and your chosen model provider — which can be a local one.
What does a Slack and X (Twitter) run leave behind?
Every run is recorded end to end — the Slack items examined, the decision and its reasoning, the resulting X (Twitter) write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
