Trigger Nodes

This page describes the Trigger nodes in the Automations workflow builder.

Trigger nodes

Purpose: Start a workflow when a specific event occurs

Characteristics:

• Every workflow must have at least one trigger

• Triggers listen for external events

• Each trigger provides a payload with event data accessible to all nodes

Available triggers: triggers are provided by Integrations. As new integrations are installed, the library of available triggers grows.

• Native triggers: Core triggers like Cron come from the Core Utilities integration.

• Integration triggers: Provided by installed apps (e.g., "New Zendesk ticket", "Email received", "Status changed").

• Extensible architecture: Since integrations are standalone services, a trigger can be anything that can interact with a web server.