> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/asana.md). # Asana ### Connection When you're setting up your first workflow with Asana, you'll need to create a connection through MESA's Asana app or use your own custom Asana app. Click on the **Connect with Asana** button.
Screenshot of the MESA Asana connection setup for your first Asana workflow. Spotlight the Connect with Asana button.
You will see a screen asking you to grant MESA permission to connect with your Asana account. Once you have reviewed the permissions, click on **Allow**.
Screenshot of the Asana permission screen asking you to grant MESA permission to connect with your Asana account. Spotlight the Allow button.
Afterwards, you will be brought back to your current workflow and you are all set! MESA is now connected with your Asana account. *** ### Configuration #### Select your Workplace, Project, or Task All Asana [triggers](/workflow-builder/triggers.md) require you to select a workspace that MESA should work with. If your Asana [trigger or action](/workflow-builder/triggers.md) contains multiple fields to select, you must click on the **Workplace** drop-down menu first.
Screenshot of an Asana trigger configuration in MESA where you select the workspace MESA should work with. Spotlight the Workplace drop-down menu.
You can also specify the **Project Gid** below the Workplace drop-down menu. Clicking on Project Gid first without selecting a workplace will display an error.
Screenshot of an Asana trigger configuration in MESA showing the Project Gid field below the Workplace drop-down menu. Spotlight the Project Gid field.
#### Start off with an Asana Task Added trigger in your MESA workflow {% hint style="info" %} When your enabled workflow starts with an Asana Task Added trigger, you will see many Skipped tasks in the workflow's Activity tab. Don't be scared! That is to be expected. 😊 {% endhint %} You will see many **Skipped** tasks since Asana sends MESA any update that occurs in any of your Asana tasks. To prevent multiple MESA tasks associated to the same update from triggering the workflow, MESA will automatically mark duplicated MESA tasks as **Skipped**. Please note that **Skipped** tasks will not impact your billing.
Screenshot of a MESA workflow Activity tab showing many Skipped tasks from an Asana Task Added trigger. Spotlight the Skipped task statuses.
When viewing the workflow's [Activity tab](/workflow-activity.md), we recommend sorting your MESA tasks by clicking on the **Status** drop-down menu to view your tasks' statuses more efficiently.
Screenshot of a MESA workflow Activity tab, sort your tasks by status. Spotlight the Status drop-down menu.
#### Update an Asana task after your workflow starts off with an Asana Task Added trigger {% hint style="danger" %} Please read the following if your workflow looks like the below screenshot. The below screenshot will cause unintended problems. {% endhint %}
Screenshot of a problematic MESA workflow that starts with an Asana Task Added trigger and updates the Asana task with no other steps, causing an infinite loop. Spotlight the workflow steps.
The **Asana Task Added** trigger not only activates when any Asana task is added but also when an Asana task is updated. Therefore, updating the Asana Task without any other steps in the workflow will cause an infinite loop between these two steps. An infinite loop will cause your workflow to run in a circle and create many MESA tasks. To prevent this, we recommend adding a [Filter](/tools/filter.md) step below your workflow's trigger. The Filter should check for whatever you plan to update the task with. If the Filter step locates the item that is used to update the task, then the Filter step will stop the automation. Your workflow should look like this now:
Screenshot of the corrected MESA workflow with a Filter step added below the Asana Task Added trigger to prevent an infinite loop. Spotlight the Filter step.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.getmesa.com/connect/asana.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.