What happens when the Attio task is completed?

This flow creates Asana tasks from open Attio tasks; it doesn't close the loop back. To mark the Asana task done when Attio's is, the agent would re-read the Attio task by id, see it's completed, and call update_tasks in Asana on the mirrored task.

Can I route different task types to different projects?

Yes. The agent can branch on the Attio task's linked object or a tag and choose the Asana project per task, so renewal follow-ups and onboarding steps land in their own boards.

AttioAsana

Turn Attio tasks into Asana tasks for the delivery team

A Attio + Asana agent flow

Sales sets follow-ups inside Attio against a deal, but the people who actually do the work, onboarding, implementation, success, run their week in Asana and never open the CRM. A task created in one system is invisible in the other. This flow mirrors them. The agent lists open Attio tasks with list-tasks, reads each one's content and due date, and creates a matching Asana task with create_tasks in the delivery project. Attio returns tasks when the agent asks, not on a push, so the agent reads on a schedule, every fifteen minutes or each morning, and an Attio task it has already mirrored is skipped on the next pass.

The flow

Attiolist-tasks

Lists workspace tasks with optional filters.

Asanacreate_tasks

Creates up to 50 tasks with assignments, dates, and custom fields.

Step by step

Open Attio tasks come back first
A list-tasks call filtered to open status returns each task's text, due date, and the record it's linked to. The Attio task id is the dedupe key.
Which ones are already mirrored
The agent keeps a record of Attio task ids it has already created in Asana, or searches Asana for the id stamped in the task notes, so it only acts on genuinely new ones.
Into the delivery project it goes
create_tasks adds the task to the chosen Asana project with the Attio task text as the name, the due date carried over, and the source Attio task id written into the notes for traceability.

Tell your agent

Every 15 minutes, list open tasks in Attio, and for each one I haven't mirrored yet, create an Asana task in the Onboarding project with the same name and due date. Put the Attio task id in the Asana task notes so we don't duplicate it.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Attio install guide Asana install guide

Worth knowing

list-tasks returns the task itself, including its text and the id of the linked record, but not the full record's details. If the Asana task needs the company name or owner, the agent makes a second call such as get-records-by-ids before writing.
create_tasks can create up to 50 tasks in one call, so batch a backlog rather than firing one request per task. But cap the first run, or an initial sync floods the delivery project with every historical follow-up.
Assignee identity differs between the two tools. The Attio owner won't map to an Asana user automatically, so either leave the Asana task unassigned for a lead to triage, or maintain an explicit email-to-Asana-user mapping.

Questions

What happens when the Attio task is completed?: This flow creates Asana tasks from open Attio tasks; it doesn't close the loop back. To mark the Asana task done when Attio's is, the agent would re-read the Attio task by id, see it's completed, and call update_tasks in Asana on the mirrored task.
Can I route different task types to different projects?: Yes. The agent can branch on the Attio task's linked object or a tag and choose the Asana project per task, so renewal follow-ups and onboarding steps land in their own boards.