Triggers

The Orchestrator supports multiple ways to trigger pipeline runs: manual triggers from the UI, API calls, webhook integrations, and advanced trigger configurations with parameterized variables.

👆 Manual Triggers

From the project page, click the Run button, select a pipeline and branch, and start the run.

🎟️ Trigger Tokens

To allow external systems to trigger runs, create a trigger token from Project Settings → Trigger Tokens. Trigger tokens are scoped to a single repository and only authorize triggering runs, no other operations.

⚙️ Trigger Configurations

Trigger configurations define reusable, parameterized triggers for a repository. They support matrix variables, environment mappings, and versioning.

Creating a Trigger Config

Navigate to Project Settings → Trigger Configs and click Create. Give it a name (e.g. nightly-build).

Adding a Version

Each trigger config can have multiple versions. Click Add Version and configure:

• Workflow path: The pipeline file to execute (e.g. build.act)
• Ref: The branch or tag to use (e.g. main)
• Matrix variables: Parameter combinations that generate multiple runs
• Environment mappings: Environment variables to inject
• Subset policy: Whether callers can trigger a subset of the matrix

Matrix Variables

Matrix variables define parameter combinations. For example, a matrix with os: [linux, macos, windows] and arch: [x64, arm64] produces 6 runs. With subset policy enabled, callers can trigger only a portion of the full matrix.

Enabling and Disabling Versions

Each version can be toggled on and off independently from the trigger config detail page. This lets you roll out new configurations without removing old ones.

API Snippets

The trigger config detail page shows ready-to-use code snippets for triggering via the API in multiple languages (Console, Python, JavaScript, Go, Ruby). Click on a token placeholder to select an existing trigger token.

🪝 Webhook Integration

To trigger runs from external systems (e.g., GitHub webhooks):

1. Create a trigger token in Project Settings → Trigger Tokens
2. Configure the external system to POST to the trigger endpoint with the token
3. Optionally create a trigger configuration for parameterized runs

For API endpoint details and examples, see REST API.