Skip to main content

​
What are Triggers?

Triggers define how a composer’s workflow is started. Each composer has a trigger type configured at the composer level. When a trigger fires, it passes contextual data into the workflow that you can access with {{trigger.*}} template variables.
The trigger does not choose which project a workflow runs against. To scope a workflow to a specific project, add a Royaltyport variable (a project reference) to the composer and reference it from your steps. When you start a run from the Start Workflow dialog, its project picker lets you choose — or override — the project for that run.

​
Trigger Types

​
Manual

Run the workflow on demand using the Run button in the composer or canvas header. Manual triggers are useful for testing and for workflows that should only run when explicitly started.

​
Event

Event triggers fire automatically when specific database events occur. The trigger data from the event is available as {{trigger.*}} in your steps. Available events:

​
Schedule

Schedule triggers run the workflow automatically based on a CRON expression. Common patterns: Enter the CRON expression in the trigger configuration panel of your composer.

Composers

Triggers are configured at the composer level.

Steps

Use trigger data in your steps with template variables.

Test & Deploy

Test your triggers before deploying to live.