Skip to main content
On Task Created runs immediately after a task of the chosen Flow is created and saved. It lets you act on a task the moment it enters the system: place it, assign it, create its partner task, notify the customer or tell another system.
Required permission:
  • View automation
  • Create automation

When it runs

The event runs when a task is created by any of these:
  • Web app: a user creates the task on the Task page.
  • Import: tasks uploaded from a spreadsheet.
  • Field app: a field worker creates the task.
  • API: a task created through the API.
  • Automation: a task created by another automation.
  • Schedule: a task generated by a recurring schedule.
It runs only when the task’s flow matches the automation’s Flow, and the task matches every rule.

Set it up

  1. On Workflow › Automation, click New.
  2. Name: for example “Create Delivery when Pickup is created”.
  3. Event: On Task Created.
  4. Flow: the flow to watch, for example Pickup.
  5. Automation Type: one of
  6. Optionally add Rules, fill in the Automation detail, and click Submit.
  7. Make sure the automation’s Active switch is on, then create a task of that flow to test it.

Use cases

Flow matching

The automation checks the flow of every new task: You can create several automations on the same event for different flows, for example On Task Created › Delivery › send to the ERP, and On Task Created › Pickup › send to the WMS. Each runs on its own.

Webhook payload

With the Webhook action, the request body carries the new task. An example:
The exact fields depend on the components of your flow. Use the Sample payload box of the webhook’s Custom JSON body to see the keys you can map. The automation log shows the exact request that was sent.

Troubleshooting

The automation doesn’t run when tasks are created.
  • Check that its Active switch is on.
  • Check that the task’s flow matches the automation’s Flow.
  • Check that the rules don’t exclude the task.
  • Open the log and look for failed runs.
The webhook receives incomplete task data.
  • Optional fields that were left empty when the task was created are not sent. Handle missing keys in your endpoint.
  • Tasks created through the API with minimal data carry only what was sent.
The automation runs more than once for the same task.
  • Look for several active automations on the same flow.
  • Make sure you chose On Task Created and not On Task Finished.
  • Make your endpoint idempotent, using the task ID.
Tasks are created in a loop.
  • An automation that creates a task of the same flow it watches triggers itself. The Create Task list doesn’t offer the trigger’s own flow, but two automations can still feed each other. Use different flows, or add rules that stop the chain.