Asana triggers start a run from what happens in a project. All four are instant — Asana tells Bizomate when it happens:

  • Asana · New task in a project — When a task is added to a project.
  • Asana · Task completed — When a task in a project is marked complete.
  • Asana · Task updated — When a task in a project changes.
  • Asana · New comment — When someone comments on a task in a project.

Publishing adds a webhook to the project for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

Before you start

An Asana connection — see Connect Asana — whose account is a member of the project.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
  2. Under Asana, select the event. It reads Asana · instant. Or type Asana in Search triggers.
  3. In Connection, choose your Asana connection.
  4. In Workspace, choose the workspace — Consulace. In Project, choose the project — Client onboarding. For New task in a project: A task moved into the project counts as new to it, as Asana sees it.
  5. For Task updated: optional, in Fields to watch, Asana's names for the fields — assignee, due_on. Asana's names for them, separated with commas — name, notes, assignee, due_on, due_at, completed, custom_fields, tags. Empty: any change. Several changes at once start one run.
  6. The panel reads Publishing sets this up in Asana, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.
  7. Add the steps, then Publish. Bizomate adds a webhook to the project. The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

  1. Make the event happen in the project — add a task, or complete one.
  2. When Asana sends it, the panel reads Listening — instant — Last event 10:45 · Task completed · Onboard Northwind Logistics.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

The task, read back from Asana as the Asana steps read it — id, name, notes, url, assignee, assigneeEmail, dueDate, completed, completedAt, createdAt, projects, section, tags, and each custom field by its name — and user, the name of whoever did it. Also:

  • Task updated: changedFields — Asana's names for what changed, ["assignee", "due_on"].
  • New comment: commentId and text — Kickoff moved to Tuesday. — and user is who wrote it.

What happens next

  • Each task starts one run of the live version, in Production, named after it — New task · Onboard Northwind Logistics, Task completed · …, Task updated · Onboard Northwind Logistics · assignee, due_on, New comment · …. Several changes to one task that Asana sends together start one run.
  • Each workflow has its own webhook on the project. Every publish sets it up again; changing to another trigger or project and publishing, or deleting the workflow, removes it.

How Bizomate knows an event is Asana's

While the webhook is being made, Asana calls Bizomate's address with a secret of its own (the X-Hook-Secret header). Bizomate answers with it and keeps it, encrypted — only then, never once the address is set up. Asana signs every event after that with the secret (the X-Hook-Signature header), and Bizomate works the signature out again. An event whose signature does not match is answered 401 — The signature does not match. — and starts nothing.

Good to know

  • Asana groups events that happen close together and may send them a little later — usually within a minute.
  • New task in a project hears tasks added to the project, including ones moved or multi-homed from another project. A subtask, or a task moved between sections, is not a new task.
  • Task completed starts nothing if the task was marked incomplete again before Bizomate read it.
  • Completing a task is also a change to it. A workflow on Task updated with Fields to watch empty runs too.
  • A task deleted before Bizomate reads it starts no run.

If something goes wrong

What you see Why What to do
Not listening — Asana would not take Bizomate's address: Choose the project the trigger listens to. Fix it, then publish again. No project is chosen. Choose the project, then publish again.
Not listening — Asana would not take Bizomate's address: Asana refused: … Fix it, then publish again. The token was deleted, or the account cannot reach the project. Replace the token, or ask to be added to the project, then publish again.
Waiting for the first event stays Nothing has happened yet, the changed field is not one you watch, or Asana has not sent it yet. Make the event happen, and allow a minute.
Nothing has arrived yet — make one happen in Asana, then try again. on Output No event has reached the trigger yet. Make one happen, wait for Listening — instant, then Use the last event.
A run did not start for an event the panel shows The workflow is switched off, or its workspace is archived. Switch it on — see Switch a workflow on or off. The missed event does not run later.