> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/install-and-configure-apps/asana-oauth-credentials/steps-in-asana.md).

# Steps in Asana

To create OAuth 2.0 credentials for Asana:

1. Log in to your Asana developers account.
2. Under **My apps**, click **Create new app**.
3. In the **Create new app** window, enter a name for your OAuth app and select any of the use cases for your app. Click **Create app**.
4. Under Configure in the left menu, click **OAuth**.
5. Click **+ Add redirect URL** and enter your OAuth redirect URI. Click **Add**.
6. Under **Test & distribute** in the left menu, click **Manage distribution**.
7. Under **Choose a distribution method**, select **Any workspace**.
8. Click **Save**.
9. Under **Configure** in the left menu, click **Basic Information**. Copy your **Client ID** and **Client secret** and store them in a secure place.
10. Optional: Upload a logo for the consent dialog. No logos appear until you upload one.

You have created the required credentials and granted all necessary access to your end users.


---

# 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://developers.make.com/white-label-documentation/install-and-configure-apps/asana-oauth-credentials/steps-in-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.
