How to integrate Unify with Asana

Before connecting

• A Unify Play with a Webhook action
• An authorized Asana identity and a destination project GID
• An agreed review action and owner

1. 01

   Choose the task location

   Use the actual project GID in data.projects. Asana requires a workspace, which can be inferred from the specified project or parent task.[3]

2. 02

   Authorize the sender

   Create a personal access token for the intended account context. Token access follows that user’s access, so validate the destination project.[4]

3. 03

   Configure the outbound request

   Use the method, endpoint, authentication, and JSON body below in the Play. Map only available fields and inspect Expand preview. The receiver must acknowledge within 8 seconds; Unify does not pass the response body into later Play steps.[1][2]

4. 04

   Inspect the created task

   Check the API’s created-task result and open it in the project. Set an assignee only after resolving the intended Asana user identity.[3]

5. 05

   Test a repeated handoff

   Decide whether another selection is new work. If a single ongoing task should be updated, use a receiver to track task identity and implement that policy.[3][2]

{
  "data": {
    "name": "Review Avery Morgan",
    "notes": "Review this fictional prospect before follow-up: avery@example.com",
    "projects": [
      "YOUR_PROJECT_GID"
    ]
  }
}

Fictional task. Replace the project placeholder and define ownership before live use. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2][3]

Map the person name into data.name and the review context into data.notes. Replace YOUR_PROJECT_GID with the actual project identifier. A prospect email is context, not an Asana assignee identifier.