Automate Google Drive + Trello
Where the documents live — and pile up. Boards and cards — simple enough to automate deeply. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Document Extractor is a ready-made agent built around Google Drive; point its last step at Trello to finish this hand-off.
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 Trello.
When a file lands in a folder in Google Drive…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a file is shared in Google Drive…
…an agent can summarise a board in Trello — after reading the context and deciding it should.
When a card is created or moved in Trello…
…an agent can read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Trello, setup template
Start with the google-drive-api node and a custom-api call to api.trello.com. Configure the Google Drive source payload, the agent input, and the Trello operation. The sequential template does not implement conditional writes or approval by itself.
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": "4e50421a-35e4-4800-a640-16464bdce8b8",
"name": "Google Drive → Trello",
"nodes": [
{
"id": "40dfeed6-52bb-48aa-acdf-8ed2d45986a0",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"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": "bc119d3a-e3de-4259-ad8e-0ae7b4cf2fc2",
"text": "Read Google Drive",
"x": 512,
"y": 336,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "LIST_FILES",
"folderId": "CONFIGURE_FOLDERID"
},
"description": "Setup template for Google Drive API. Interact with Google Drive to perform various operations on files and folders. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "692421a7-e987-49ca-a5ca-25af21a7b9c4",
"text": "Review source and draft",
"x": 512,
"y": 528,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Drive item. Decide whether it warrants action in Trello, and explain why.\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": "d7aaf6f7-bf30-4627-a29b-ef848ccb8596",
"text": "Call Trello",
"x": 512,
"y": 720,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.trello.com/1/cards?key={key}&token={token}",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "24b49bb7-f7b3-45bb-a1c3-0cc8622cdc2a",
"start": {
"id": "40dfeed6-52bb-48aa-acdf-8ed2d45986a0",
"type": "output"
},
"end": {
"id": "bc119d3a-e3de-4259-ad8e-0ae7b4cf2fc2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b4ed258a-efb7-44d2-a40f-2540e1f92674",
"start": {
"id": "bc119d3a-e3de-4259-ad8e-0ae7b4cf2fc2",
"type": "output"
},
"end": {
"id": "692421a7-e987-49ca-a5ca-25af21a7b9c4",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
},
{
"id": "4a5ed1f3-db6c-4b41-a765-c82a22d5b052",
"start": {
"id": "692421a7-e987-49ca-a5ca-25af21a7b9c4",
"type": "output"
},
"end": {
"id": "d7aaf6f7-bf30-4627-a29b-ef848ccb8596",
"type": "input"
},
"startX": 800,
"startY": 552,
"endX": 512,
"endY": 744
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Drive API
Interact with Google Drive to perform various operations on files and folders.
- action — The action to perform on Google Drive Current example:
LIST_FILES. - folderId — The ID of the folder (for LIST_FILES, UPLOAD_FILE, CREATE_FOLDER) Current example:
CONFIGURE_FOLDERID.
Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://api.trello.com/1/cards?key={key}&token={token}. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install Document Extractor
Document Extractor is a working agent built around Google Drive. Install it, point its last step at Trello, 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
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Trello (an API key pasted into the vault) and Google Drive (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-drive-api does the reading and custom-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Google Drive and Trello — common questions
Can I connect Google Drive to Trello without writing code?
No code is required. Add both connections in the vault (Google Drive uses one OAuth sign-in, Trello uses an API key pasted into the vault), 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 Google Drive to Trello automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Google Drive item in full and decides — whether it matters, how to summarise it, and what belongs in Trello. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Google Drive and Trello 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: Google Drive, Trello, and your chosen model provider — which can be a local one.
What does a Google Drive and Trello run leave behind?
Every run is recorded end to end — the Google Drive items examined, the decision and its reasoning, the resulting Trello write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
