DEV

Asana

Asana Connection

Try @HumanBuy @Human SubscriptionJoin @Human Community

Put Asana to Work with @Human Automations and @Human Agents

The Asana Connection documents all Triggers, Actions and Query Operations available for creating automations via the Asana API.

What can you do with the Asana Connection?

  • Connect to the Asana API in a few clicks

  • Use the related Asana Operations (see below) in @Human Automations or @Human Agents

Trigger Operations

Task Created

Triggers on: tasks/task_created

Triggers when a new task is created in Asana.

Task Updated

Triggers on: tasks/task_updated

Triggers when an existing task is updated in Asana.

Project Created

Triggers on: projects/project_created

Triggers when a new project is created in Asana.

Action Operations

Action: Create a Project

Action: Update a Project

Action: Create a Task

Action: Update a Task

Query Operations

Query: Get a Project

Query: Get a Task

Example link

Obtaining Access Credentials

To obtain a Personal Access Token (PAT) for Asana, follow these steps:

Prerequisites

  • An Asana account (free or paid).

  • Admin permissions (if creating tokens for an organization).

Steps

  1. Log in to your Asana account at asana.com.

  2. Click your profile icon (top-right) → Settings.

  3. Go to the Apps tab.

  4. Under Build new apps, click View developer console.

  5. Under Personal access tokens, Click Create New Token.

  6. Enter a name (e.g., "API Integration") and set expiration (optional).

  7. Click Create Token.

  8. Copy the token immediately (it won’t be shown again).

  9. Done. Use the token in API requests as a Bearer Token in the Authorization header.

Configuring Webhooks

  1. Prepare a publicly accessible listener URL (HTTPS) to receive event notifications.

  2. Implement the handshake response to echo the X-Hook-Secret header back to Asana during the verification request.

  3. Register the webhook by making an authenticated POST request to https://app.asana.com/api/1.0/webhooks.

  4. Use your Personal Access Token (PAT) as a Bearer Token in the Authorization header.

  5. Specify the resource ID (e.g., GID of a project or workspace) and the target URL in the JSON payload.

  6. Verify activation by checking for a 201 Created status from Asana once the handshake is successful.

Code (Apache v2.0): Service Connectivity and Metadata

Code (Apache v2.0): List of External Resources and Internal Mapping

Last updated