Automate Google Drive + X (Twitter)
Where the documents live — and pile up. 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.
Content Producer already works across Google Drive and X (Twitter) — free, and it runs on your machine.
Automations teams run
These are not field mappings. An agent reads the Google Drive side, works out what it means, and only then decides what — if anything — should happen in X (Twitter).
When a file lands in a folder in Google Drive…
…an agent can post threads and replies in X (Twitter) — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can collect engagement metrics in X (Twitter) — after reading the context and deciding it should.
When a file is shared in Google Drive…
…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 read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a schedule fires in X (Twitter)…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to X (Twitter), in three nodes
Concretely: the google-drive-api node on one side, the twitter-api node on the other, and an agent in between that can decline. Deciding not to write into X (Twitter) is a recorded outcome, not a silent one.
{
"id": "1113fce9-3c85-4877-a244-ef1041b65762",
"name": "Google Drive → X (Twitter)",
"nodes": [
{
"id": "6ce5a2fc-3822-41da-ac7b-16680e146568",
"text": "Watch Google Drive",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Interact with Google Drive to perform various operations on files and folders.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "d40ced80-6549-4ec8-ae70-bd92d7d9ca74",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Drive item. Decide whether it warrants action in X (Twitter), and explain why."
},
"description": "Decides whether this Google Drive item warrants anything in X (Twitter).",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "3168c81d-0cd5-47b4-ad5e-fea578abedac",
"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": "8cd4b763-79d4-413b-a3bd-fc66b8db8856",
"start": {
"id": "6ce5a2fc-3822-41da-ac7b-16680e146568",
"type": "output"
},
"end": {
"id": "d40ced80-6549-4ec8-ae70-bd92d7d9ca74",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "107f407f-0dc9-423e-a2cd-12a1bf7728e8",
"start": {
"id": "d40ced80-6549-4ec8-ae70-bd92d7d9ca74",
"type": "output"
},
"end": {
"id": "3168c81d-0cd5-47b4-ad5e-fea578abedac",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Content Producer
Content Producer already uses both Google Drive 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 — Google Drive 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).
Google Drive and X (Twitter) — common questions
Can I connect Google Drive to X (Twitter) without writing code?
Yes. Google Drive 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 file lands in a folder, post threads and replies” — and the agent handles the rest.
How is this different from a field-mapping Google Drive to X (Twitter) automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles auto-summarise incoming docs the way a colleague would — reading the Google Drive context, judging it, then writing to X (Twitter) with the reasoning recorded.
Does my Google Drive and X (Twitter) data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Drive or X (Twitter) tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Google Drive and X (Twitter) run leave behind?
You get an auditable trail rather than a success flag. It shows the Google Drive context the agent worked from, the judgment it made about published work becomes native threads, and the exact change applied in X (Twitter), with approvals attached where you required them.
