> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/integrations/asana.md).

# Asana

Connect Luciq with Asana to automatically create tasks from mobile bug reports and crashes. Keep app monitoring in sync with your Asana workspace.

This integration will allow you to create tasks on Asana's dashboard for the bugs you receive on Luciq. Instead of switching between dashboards, forward bugs directly to Asana to track progress hassle

{% stepper %}
{% step %}
**Enter your token**

Enter your token. If you don't currently have one, click on *here* (link is provided in the integrations screen) and follow the instructions.

Click on *Manage Developers Apps*.
{% endstep %}

{% step %}
**Create a personal access token**

Create a new personal token and enter it in the integrations screen on your Luciq dashboard.
{% endstep %}

{% step %}
**Choose Workspace, Project, and Assignee**

Choose the Workspace Name, Project, and Assignee. You can also choose which details get forwarded as well.
{% endstep %}

{% step %}
**Test the integration**

Test your integration to confirm everything is working smoothly.
{% endstep %}

{% step %}
**Finish setup**

All done! Your integration is now set up and ready to go. From this final page, you can allow automatic forwarding (this can be reconfigured at any time).
{% endstep %}

{% step %}
**Example forwarded issue**

Issues forwarded to Asana should look something like this.
{% endstep %}
{% endstepper %}


---

# 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.luciq.ai/product-guides-and-integrations/integrations/asana.md?ask=<question>&goal=<user_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.