Connect Asana to coding agents

1. Create an Asana token

In Asana open the personal access-token area, create a token named Denly, copy it immediately, and confirm the account can read the target project. Read Asana personal access tokens.

2. Create the Denly connection

Open Workspace → Integrations → Connect → Asana. Use the workspace/project identifier, token, project scope, trigger tag denly, and Plan first. Leave create disabled initially.

Routing is optional. Leave Default Denly assignee blank for unassigned tasks, or choose one workspace member to own everything from this connection.

For per-person routing use Route by external assignee: each row pairs one person in the provider (left) with a workspace member (right), and + adds another row. Routing follows the item's assignee in the provider, not whoever created it, and a matching row beats the default above.

The left-hand value must be the identifier the provider actually sends, which the field's placeholder names for you. Matching ignores surrounding spaces and letter case, but nothing else: a near-miss routes nothing and looks the same as a broken integration.

Do not invent an inbound secret: Asana supplies X-Hook-Secret during registration and Denly stores it.

3. Register the webhook

Create an Asana webhook for the target project with Denly’s generated URL. Asana sends an X-Hook-Secret handshake; Denly echoes it and stores it. Only enable production events after the handshake succeeds. Read Asana webhooks.

4. Test and troubleshoot

Add denly to an Asana task or assign it to a mapped user. Asana's event carries little more than an ID, so Denly fetches the task before it can judge it. Skipped means the fetched tags, project, assignee or create rule declined it. Failed with a permission error means the token cannot read the task. An empty list means the handshake secret is stale – re-register the webhook so Asana sends a fresh one.