Back to Help Center

Connect to events (Triggers)

A trigger connects an automation to a system event. When that event occurs, the automation runs automatically.

For example: when a form is approved, when a task changes status, or when a workflow is created.

How does it work?

  1. From the Triggers window, click + to create a new connection.
  2. Select the automation you want to execute (only standalone automations are shown).
  3. Select the event that will trigger it.
  4. Configure the parameter mapping: where each value the automation needs comes from.

Parameter mapping

Each automation parameter must receive a value. In the context of a trigger, values can come from:

  • Object that triggered the event: for example, if the event is "task completed", you can map the task parameter to the object that fired the trigger.
  • Object fields: name, status, associated site, etc.
  • Constant value: a fixed value that will always be the same.
  • Trigger input parameters: additional data available in the event context.

If any parameter is left unassigned, the system shows a warning. All required parameters must have a configured value.

Reusability

A single automation can have multiple triggers. For example, you can connect the same "notify responsible by email" automation to:

  • The "task created" event in the corrective maintenance template
  • The "form approved" event in the inspection template
  • A global status change event

Each trigger has its own parameter mapping, adapted to the event context.

Available events

Triggers can be configured for different entity types and events:

Status changesActivity assignmentsObject creation
formsteam (role) assignedforms
tasksuser assignedtasks
workflowssupplier (contractor) assignedworkflows
quotessupplier user assigned
custom fields
milestones
engineering forms

Trigger management

From the Triggers window you can:

  • View all connections between automations and events
  • See the status of each connection (active/inactive, automation published, parameters configured)
  • Activate or deactivate triggers individually or in bulk
  • Delete connections that are no longer needed