Inputs
None. The Task created trigger has no configurable inputs. It watches every task in the workspace. You cannot scope it to a single object, list, or assignee from the trigger itself. To narrow the scope, add a Filter as the first step instead.Outputs
You can reference these outputs in a later block. Use
{{ steps.task_created.task.content }} for the new task’s text, {{ steps.task_created.actor }} for the actor, and {{ steps.task_created.timestamp }} for the creation time.
Behavior
The trigger fires once per task, the moment the task is created. So if a workflow creates several tasks in a single run, you get several separate Task created runs. There is one run for each task. The actor tells you the true origin of the task. The actor is whoever or whatever created it. A task a teammate adds by hand shows that person as the actor. A task created by another workflow shows that workflow as the actor. You can filter on the actor to keep automated tasks from re-triggering automated work. The trigger carries the task’s data as it exists at creation time. Later edits do not re-fire it. Suppose a step or a person changes the task’s due date or assignee afterward. The trigger stays silent, because Task created responds only to creation, not to updates.Gotchas
- The trigger is workspace-wide. It fires for every task in the workspace, including tasks that have nothing to do with the process you care about. Add a Filter as the first step to keep only the tasks you want. For example, keep tasks whose text contains
handoff, or tasks linked to a deal. - Creating tasks from this workflow can loop. Suppose a workflow is triggered by Task created and itself runs Create task. It re-triggers itself. The result is noisy task chains or an infinite loop. To prevent this, filter the actor so the workflow ignores tasks created by a workflow. You can also branch with an If block before any Create task step.
- It does not fire on task completion. Marking a task complete is an update, not a creation, so this trigger stays silent. Task created responds only to the moment a task is created. To mark a task done from inside a workflow, use Complete task in a workflow driven by whatever signal you act on.
Examples
Notifying an owner when a handoff task appears
This workflow watches for handoff tasks and pings the linked account owner, so nothing stalls in the queue.
When a member creates a task reading
Customer handoff: Acme renewal, the account owner receives a message in #revenue naming the task. Tasks created by other workflows are ignored.
Classifying new tasks by type
This workflow reads each new task’s text and routes it down a branch based on what kind of work it describes.Renewal check-in: jane@acme.com. Classify text labels it renewal. The If branch then adds the linked company to the Renewals at risk list.