Search our knowledgebase

Cynoia team

Automation Triggers Explained

A trigger listens for a specific event on a task. When that event happens, Cynoia checks the automation’s conditions (if any) and then runs the defined actions.

A trigger listens for a specific event on a task. When that event happens, Cynoia checks the automation’s conditions (if any) and then runs the defined actions.

Written by : Cynoia team

Last Updated on 29 January 2026

Automation triggers define when an automation starts.

A trigger listens for a specific event on a task. When that event happens, Cynoia checks the automation’s conditions (if any) and then runs the defined actions.

Each automation can have one trigger.

What Is a Trigger?

A trigger is the starting point of an automation.

Example:

  • When a task status changes

  • When a new task is created

  • When a file is uploaded to a task

Triggers react to real-time changes inside a project.

Available Automation Triggers

Below is the full list of triggers currently available in Cynoia.

Task Creation Triggers

These triggers react when tasks or subtasks are created.

  • New task is created

    Starts the automation when a new task is added to the project.

  • New subtask is created

    Starts the automation when a subtask is added to an existing task.

Task Status Triggers

These triggers react to changes in task status.

  • Task status changes

    Starts the automation when a task moves from one status to another

    (e.g. In Progress → Completed)

Common use cases:

  • Notifications on completion

  • Workflow enforcement

  • Status-based actions

Task Priority Triggers

  • Task priority is set

    Starts the automation when a priority is assigned or changed.

Useful for:

  • Escalating urgent work

  • Auto-assigning high-priority tasks

Label & Assignment Triggers

  • Task is assigned a label

    Starts the automation when a label is added to a task.

  • Task is assigned to

    Starts the automation when a task is assigned to a user.

Content & Activity Triggers

These triggers react to task activity and content changes.

  • Task comment is added

  • Task name changed

  • Task description changed

  • File uploaded to task

Common use cases:

  • Notify stakeholders

  • Track updates

  • Enforce documentation rules

Task Deletion Trigger

  • Task gets deleted

    Starts the automation when a task is removed from the project.

Budget & Expense Triggers

These triggers are available when Budget is enabled in the project.

  • Budget threshold reached

    Triggered when the project reaches a predefined budget limit.

  • Expenses exceed budget

    Triggered when expenses go over the allocated budget.

How Triggers Work with Conditions

Triggers define when something happens.

Conditions define which tasks the automation applies to.

Example:

  • Trigger: Task status changes

  • Condition: Task priority = Urgent

This ensures the automation only runs for specific cases.

Best Practices for Choosing Triggers

  • Choose specific triggers to avoid unnecessary automations

  • Combine triggers with conditions for precision

  • Avoid using triggers that fire too frequently unless needed

  • Test triggers with sample tasks before enabling

Common Trigger Use Cases

  • Notify the team when tasks are completed

  • Assign tasks automatically on creation

  • Escalate urgent or blocked tasks

  • Monitor budget and expenses

What’s Next?

Now that you understand triggers, let’s move on to:

👉 Next article: Automation Conditions Explained