AI agents for X (Twitter)
The feed where your market thinks out loud. AGNT connects to X (Twitter) so agents can read what happens there, reason about it, and act — with a receipt for every run.
Social Scheduler is a ready-made agent that works in X (Twitter) — free, and it runs on your machine.
X (Twitter) and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in X (Twitter). |
|---|---|
| Connects with | One OAuth sign-in |
| AGNT node | twitter-api |
| Runs when | A mention or keyword appears |
| 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 mention or keyword appears
- a schedule fires
Agents can…
- post threads and replies
- collect engagement metrics
Teams use it for
- published work becomes native threads
- brand mentions briefed daily
- engagement reported without screenshots
Copy this X (Twitter) workflow
Design goal for X (Twitter): published work becomes native threads; brand mentions briefed daily; engagement reported without screenshots. The template below supplies configurable nodes, not the complete logic for those goals.
Use this X (Twitter) setup template to arrange the schedule, input review and API operation. Configure the account-specific fields and add your own decision and approval controls before activation.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "c1e78d1a-da86-4310-af97-9d8424da3964",
"name": "X (Twitter) — read, decide, act",
"nodes": [
{
"id": "aaca2652-77ab-4ffb-ab1f-71476eda8046",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "clock",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3e233136-7799-4750-a461-dd5edb771f30",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the X (Twitter) item and decide whether it warrants action. Explain your reasoning.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "c8360c52-9114-4b15-a32b-57292a27648a",
"text": "Configure destination in X (Twitter)",
"x": 512,
"y": 528,
"isEditing": false,
"type": "twitter-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "POST",
"text": "CONFIGURE_TEXT"
},
"description": "Setup template for X (Twitter) API. Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "c31be0a3-5c8a-4b72-a9bb-4c0b50c8bdf0",
"start": {
"id": "aaca2652-77ab-4ffb-ab1f-71476eda8046",
"type": "output"
},
"end": {
"id": "3e233136-7799-4750-a461-dd5edb771f30",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "3e50c8da-9d71-4de1-afa9-d36be2825c36",
"start": {
"id": "3e233136-7799-4750-a461-dd5edb771f30",
"type": "output"
},
"end": {
"id": "c8360c52-9114-4b15-a32b-57292a27648a",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}
Configure X (Twitter) API
Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.
- action — The action to perform on Twitter Current example:
POST. - text — The content of the tweet, reply, or quote tweet Current example:
CONFIGURE_TEXT.
Install Social Scheduler — it runs on X (Twitter)
Social Scheduler is a working agent that uses X (Twitter). Installing it drops the whole workflow onto your canvas — connected, editable, and yours to change.
Runs on your own machine · See what it does
Publishing that is native, not pasted
A thread that works is written as a thread — a first line that earns the second, one idea per post. An agent adapting long-form work into that shape produces something worth reading, which reposting a paragraph never does.
Listening as an input
The same connection watches mentions and keywords, which makes it a monitoring source as much as a publishing destination. What your market says out loud is research, provided somebody reads it consistently.
X (Twitter) node reference
Interact with Twitter to post, quote, reply, delete, retrieve tweets, search, manage follows, and fetch profiles/conversations.
What it can do: POST DELETE REPLY QUOTE_TWEET LIKE UNLIKE RETWEET UNRETWEET GET_ME GET_TWEET GET_TWEETS GET_TIMELINE SEARCH ADVANCED_SEARCH GET_PROFILE GET_CONVERSATION MONITOR_REPLIES CHECK_MENTIONS FOLLOW UNFOLLOW BULK_UNFOLLOW
Full X (Twitter) API parameter reference
| Parameter | Type | What it does |
|---|---|---|
actionrequired |
string | The action to perform on Twitter POST · DELETE · REPLY · QUOTE_TWEET · LIKE · UNLIKE · RETWEET · UNRETWEET |
text |
string | The content of the tweet, reply, or quote tweet only when action is POST or REPLY or QUOTE_TWEET |
tweetId |
string | The tweet ID or X/Twitter URL to delete, reply to, like/unlike, quote, retweet/unretweet, fetch, or monitor replies for only when action is DELETE or REPLY or QUOTE_TWEET or LIKE |
userId |
string | The user ID, username, @handle, or profile URL to fetch tweets, timeline, or profile only when action is GET_TWEETS or GET_TIMELINE or GET_PROFILE |
targetUserId |
string | The target user ID, username, @handle, or profile URL to follow or unfollow only when action is FOLLOW or UNFOLLOW |
userIds |
array | Array of user IDs or usernames to unfollow (max 100) only when action is BULK_UNFOLLOW |
maxResults |
number | The maximum number of results to return only when action is GET_TWEETS or GET_TIMELINE or SEARCH or ADVANCED_SEARCH |
query |
string | The search query for finding tweets only when action is SEARCH or ADVANCED_SEARCH |
sortOrder |
string | How to sort the search results RECENCY · POPULARITY only when action is SEARCH or ADVANCED_SEARCH |
conversationId |
string | Conversation ID to fetch when using GET_CONVERSATION without a root tweet ID only when action is GET_CONVERSATION |
startTime |
string | ISO timestamp lower bound for ADVANCED_SEARCH only when action is ADVANCED_SEARCH |
endTime |
string | ISO timestamp upper bound for ADVANCED_SEARCH only when action is ADVANCED_SEARCH |
10 further parameters are available on the node itself.
Every parameter above is read from the shipped twitter-api node, so it cannot drift from the product.
Connect X (Twitter) 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 X (Twitter) node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
X (Twitter) + AGNT — common questions
Can an agent post automatically?
It can, though approval-then-schedule is the recommended shape for anything public.
Can it monitor mentions?
Yes — mentions and keywords can trigger a run or feed a scheduled briefing.
Can engagement be reported?
Yes, collected back into the same reporting as everything else.