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

# Asana

Link customer issues in Pylon to tasks in Asana

## Setup <a href="#setup" id="setup"></a>

Click into the App Directory from your Pylon dashboard and then click on the Asana integration to view setup instructions.

## Usage

### Creating Asana Tasks <a href="#creating-tickets" id="creating-tickets"></a>

From a Pylon issue, you’ll see an Asana Details module in the sidebar. You can find an existing issue by copying in a link to it directly, or searching by keywords.

To create a new task, select a project and click Create.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-create-or-search.png" alt=""><figcaption></figcaption></figure>

Your form should popup. We’ve copied the Pylon ID into your clipboard for you to copy into the Pylon Issue ID field. The first time you create a ticket, you will need to allow clipboard browser permissions for Pylon.

Copy the ID into that field.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-asana-form.png" alt=""><figcaption></figcaption></figure>

And you’re done! Notice how the ticket has a Pylon native module embedded right there so your product and engineering can also get context on the Pylon side of things.

<figure><img src="https://mintlify.s3-us-west-1.amazonaws.com/pylon/images/product-ticketing-asana-ticket.png" alt=""><figcaption></figcaption></figure>

### Linking Asana Tasks <a href="#try-it-out" id="try-it-out"></a>

You can also search for an Asana task by keywords, or directly paste in a link to the task.

### Inside Pylon

Comments in Asana sync as internal notes to Pylon and comments on the Asana internal thread from Pylon sync back to Asana as comments on the ticket.

In addition, when a Asana task is completed, the Pylon issue receives a notification and gets moved to "On You", letting you know to tell the customer about completed change.


---

# 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.usepylon.com/pylon-docs/integrations/ticketing/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.