Automate Linear + X (Twitter)
Fast issue tracking that deserves fast automation. 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.
Meeting Follow-Through is a ready-made agent built around Linear; point its last step at X (Twitter) to finish this hand-off.
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 Linear into X (Twitter).
When an issue is created in Linear…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a status changes in Linear…
…an agent can collect engagement metrics in X (Twitter) — after reading the context and deciding it should.
When a cycle ends in Linear…
…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 create issues with full context in Linear — with the reasoning recorded in the run’s receipt.
When a schedule fires in X (Twitter)…
…an agent can update status and assignees in Linear — with the reasoning recorded in the run’s receipt.
Copy this Linear → X (Twitter) workflow
Linear is reached through a custom-api call to api.linear.app and X (Twitter) through the twitter-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.
{
"id": "9a024763-564a-4398-aab4-d5f1823cada0",
"name": "Linear → X (Twitter)",
"nodes": [
{
"id": "6dcfe57a-e191-48ae-a3e5-6594435f8e28",
"text": "Poll Linear",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"interval": "15",
"unit": "minutes"
},
"description": "Checks Linear on a schedule.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "cd10e2d5-d356-4975-a8e5-3faec2af2ec2",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Linear item. Decide whether it warrants action in X (Twitter), and explain why."
},
"description": "Decides whether this Linear item warrants anything in X (Twitter).",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3c6d3aa3-48b7-4dae-a4eb-746344d95da0",
"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": "83274b75-ab41-4629-a458-f028ba147136",
"start": {
"id": "6dcfe57a-e191-48ae-a3e5-6594435f8e28",
"type": "output"
},
"end": {
"id": "cd10e2d5-d356-4975-a8e5-3faec2af2ec2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "1ee6f1c0-e070-4e08-aac6-f78800b4960c",
"start": {
"id": "cd10e2d5-d356-4975-a8e5-3faec2af2ec2",
"type": "output"
},
"end": {
"id": "3c6d3aa3-48b7-4dae-a4eb-746344d95da0",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Linear. Install it, point its last step at X (Twitter), and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Download AGNT Community Core — free and local-first.
- Connect Linear with an API key pasted into the vault and X (Twitter) with one OAuth sign-in; both land in the local vault.
- Start from a marketplace workflow, or drop a custom-api node and twitter-api onto the canvas with an agent between them.
- Put an approval gate on anything consequential, then run it — the receipt shows what was read in Linear and what was written to X (Twitter).
Linear and X (Twitter) — common questions
Can I connect Linear to X (Twitter) without writing code?
No code is required. Add both connections in the vault (Linear uses an API key pasted into the vault, X (Twitter) uses one OAuth sign-in), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping Linear 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 Linear, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Linear and X (Twitter) data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Linear, X (Twitter) and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Linear and X (Twitter) run leave behind?
Every run is recorded end to end — the Linear 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.
