> ## Documentation Index > Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt > Use this file to discover all available pages before exploring further. # Asana > Connect Asana so an agent can pick up work from tasks in your projects, process attached files, and comment back. Connecting Asana lets an agent pick up work from tasks. Someone adds a task to a project the agent watches, or comments on one, and the agent handles it: reading attached files, doing the work, and commenting back on the task. Any custom agent can have Asana triggers, each scoped to the projects, sections, tags, or assignees it should care about, so one Asana account can feed several agents, each with its own instructions and permissions. ## Set up Asana Before you begin: | Requirement | Detail | | :- | :- | | In Conversion | Permission to manage integrations | | In Asana | An Asana account that can see the projects your agents should watch | The agent acts in Asana as the account you connect: its comments and task changes show that account's name. Asana has no separate identity for apps, so Conversion ignores events made by the connected account. Otherwise the agent would wake itself up every time it commented. > [!TIP] > > Connect a dedicated Asana account, such as a "Conversion Agent" user, rather than your own. If you connect your own account, the agent never sees your comments or edits. 1. Go to **Workspace settings → AI → Connections**. 2. Find **Asana** under **Integrations** and click **Connect**. 3. Read the note about which account to use, then click **Continue**. 4. Sign in to Asana with the account the agent should use, and approve the access Conversion asks for. A Conversion workspace connects one Asana account. Connecting a different account replaces it, and Conversion moves its project subscriptions to the new account. Onboarding with Conversion? Let your Deployment Strategist know when this is done and we'll check it on our end. *** ## Choosing which tasks an agent picks up An Asana trigger has an event, one or more projects, and optional filters. ### Projects Asana only reports task activity to apps that watch a specific project, so every Asana trigger watches at least one project (up to 20). When you save the trigger, Conversion subscribes to those projects. If Asana refuses, for example because the connected account can't see a project, the trigger isn't saved. Check that the connected account can see every project in the trigger, then save again. If the connected account belongs to more than one Asana workspace, pick the workspace first, then its projects. ### Event types | Event | Fires when | | :- | :- | | **Task added to project** | A task is created in a watched project, or an existing task is added to one | | **Task updated** | A task in a watched project changes, including moving to another section | | **Comment added** | Someone comments on a task in a watched project | | **Task moved to section** | A task enters one of the sections in the trigger's **Section** filter, or is created in one | | **Task assigned to agent** | A task is assigned to the connected Asana account, or created assigned to it | **Comment added**, **Task moved to section**, and **Task assigned to agent** are usually the best choices. Each fires only when a person deliberately hands the agent work, and the same trigger handles follow-up comments later in the conversation. **Task moved to section** needs a **Section** filter. It fits a board where a column such as "Ready for agent" means the work is ready. **Task added to project** waits until the new task goes 30 seconds without changes, up to two minutes, so the agent starts once with the description, assignee, and fields someone fills in right after creating it. Those edits count as one update, so a **Task updated** trigger picks up the new task too, once. > [!WARNING] > > **Task updated** fires on edits like renaming, reassigning, or changing a due date. Each one interrupts whatever the agent was doing. Avoid it unless you specifically want that. ### Filters | Filter | Narrows to | | :- | :- | | **Section** | Tasks in the sections you pick, in the trigger's projects | | **Tag** | Tasks carrying any of the tags you pick | | **Assignee** | Tasks assigned to the people you pick | | **Completion** | Complete or incomplete tasks | All the filters you set must match; within one filter, any value you picked matches. So tag `agent` or `urgent`, **and** section Ready. > [!TIP] > > A dedicated tag is the clearest way to scope an agent. Make a tag like `conversion-agent`, filter on it, and the agent picks up exactly the tasks someone deliberately tagged. Renaming a project, section, or tag keeps your triggers working. Deleting one leaves a filter that can never match, and deleting a watched project stops the trigger, with no error. *** ## Working with files Files attached to the task are available to the agent. Files that Asana links from another service, such as Google Drive or Dropbox, can't be downloaded. See [Files and sandbox](https://docs.conversion.ai/product-docs/conversion-ai/files-and-sandbox.md). ## What the agent writes back | Action | Scope | | :- | :- | | **Comment** | On the triggering task only | | **Complete or reopen** | The triggering task only | | **Move to a section** | The triggering task only, within the projects it's already in | These actions are locked to the task that started the session. An agent can't comment on or change a different task, even if asked to. *** ## Several agents, one task Each agent with a matching trigger gets its own session on the same task. Several agents can work one task independently, each with its own conversation and its own comments. If you'd rather one agent handled a given kind of task, scope them with different tags or sections. *** ## Things to know ### It won't reply to itself Comments and task changes made by the connected Asana account don't wake any agent, whether the agent or a person made them. ### Pausing stops new turns on existing tasks A paused agent does not respond to new comments or updates, including on tasks it already picked up. Activate it again to continue those sessions with new events. See [Triggers](https://docs.conversion.ai/product-docs/conversion-ai/agents/triggers.md#pausing-an-agent). ### Assigning to the agent stops when you reassign A **Task assigned to agent** session continues while the task stays assigned to the connected account. Reassign the task to someone else and the agent stops responding to it. Likewise, a **Task moved to section** session stops when the task leaves the trigger's sections. ### Filters are checked on every event The trigger's event decides what starts a session. After that, any update or comment on the task continues the same session, so one trigger is enough. If a task leaves the trigger's projects or stops matching its filters, the agent stops responding. If the task matches again later, the agent continues the same session rather than starting a new one. *** ## Related > **[Triggers](https://docs.conversion.ai/product-docs/conversion-ai/agents/triggers.md)** > > Every way an agent can start. > **[Files and sandbox](https://docs.conversion.ai/product-docs/conversion-ai/files-and-sandbox.md)** > > What an agent can do with an attached file. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.