Asana

An Asana webhook delivers task lifecycle events from Asana into Plural. After you configure the source once, you can attach it to one or more workbench triggers to start jobs based on task changes.

This guide uses the Plural Console UI. For general webhook behavior and trigger configuration, see Webhooks.

Prerequisites

Before you begin, make sure you have:

• An Asana workspace with tasks or projects you want to monitor.
• Permission in Plural Console to create a webhook source and configure workbench triggers.
• Access to the Asana API to create webhook subscriptions. Asana webhooks are created programmatically through the Asana API, not through the Asana web UI.

Capabilities

Asana webhooks deliver task lifecycle events:

• Task created — a new task is created in the subscribed resource.
• Task updated — task fields such as name, notes, assignee, due date, or custom fields are modified.
• Task completed — a task is marked as complete.
• Task deleted — a task is removed from the workspace.

Plural accepts both standard Asana webhook event payloads (which include an events array with resource identifiers) and enriched payloads that include full task data.

Inbound events are stored as issues in Plural and do not start a job until a workbench trigger matches the payload content. See Webhook triggers for binding events to workbenches.