Automate Asana + Trello
Team tasks, due dates and the follow-through between them. 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.
Meeting Follow-Through is a ready-made agent built around Asana; point its last step at Trello 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 Asana into Trello.
When a task is created or completed in Asana…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a due date nears in Asana…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a project updates in Asana…
…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 create tasks with owners in Asana — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can update status and comments in Asana — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can roll up project summaries in Asana — with the reasoning recorded in the run’s receipt.
Copy this Asana → Trello workflow
Start with a custom-api call to app.asana.com and a custom-api call to api.trello.com. Configure the Asana 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": "0e821ec8-9879-449e-a87e-e07cc00100a8",
"name": "Asana → Trello",
"nodes": [
{
"id": "bfa71f1d-cc51-427f-a2d0-6484ff4adbe6",
"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": "4a166a90-4c21-4878-a6b6-a83c4823e250",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Asana 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": "e983f0b8-f139-44f1-a294-c74fe82495a2",
"text": "Call Trello",
"x": 512,
"y": 528,
"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": "6000a623-7945-4378-acc4-886b396961bc",
"start": {
"id": "bfa71f1d-cc51-427f-a2d0-6484ff4adbe6",
"type": "output"
},
"end": {
"id": "4a166a90-4c21-4878-a6b6-a83c4823e250",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "def2c153-d18c-4eaf-a30f-f6246c3bbd52",
"start": {
"id": "4a166a90-4c21-4878-a6b6-a83c4823e250",
"type": "output"
},
"end": {
"id": "e983f0b8-f139-44f1-a294-c74fe82495a2",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}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 Meeting Follow-Through
Meeting Follow-Through is a working agent built around Asana. 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
Build it in AGNT
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Trello (an API key pasted into the vault) and Asana (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; custom-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.
Asana and Trello — common questions
Can I connect Asana to Trello without writing code?
You can build it entirely from the canvas. Authorise Asana with one OAuth sign-in, Trello with an API key pasted into the vault, then tell the agent what meeting decisions become assigned tasks should look like once Trello is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Asana to Trello automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Asana 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 Asana and Trello data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Asana or Trello 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 Asana and Trello run leave behind?
You get an auditable trail rather than a success flag. It shows the Asana context the agent worked from, the judgment it made about email requests become cards instantly, and the exact change applied in Trello, with approvals attached where you required them.
