Last updated:
About Configuring Triggers
Configure triggers to define when an automation runs. Each trigger responds to specific events like Slack messages, failed checks, GitHub activity, Linear changes, or scheduled times. When an event matches your trigger configuration, the automation executes with variables populated from that event.
Add a Trigger
- Click Add Trigger in the automation editor.
- Select the trigger type from the dropdown.
- Fill in the filter fields to specify which events should match.
- Review the available variables you can use in your prompt.
You can add multiple triggers to one automation. The first trigger that matches an incoming event will fire the automation.
Trigger Types
The Trigger type dropdown groups the trigger types by where the event comes from. Each group has its own page with the configuration fields, variables, and an example prompt for every trigger type:
| Group | Trigger types |
|---|---|
| Dash0 | Schedule, Failed Check, Webhook |
| Slack | Message, Reaction |
| GitHub | Pull Request, Push, Workflow Run, Workflow Job, Workflow Dispatch, Check Run, Check Suite, Deployment, Deployment Status, Release |
| GitLab | Merge Request, Comment |
| Linear | Mention, Issue, Issue Comment, Issue Attachment, Comment Reaction, Project, Project Update, Initiative, Initiative Update, Release, Release Note |
Scroll the trigger menu to the GitHub: CI and GitHub: CD groups to choose events such as Push, Workflow Run, Check Run, or Release. The menu also includes Darkplane AutoMerge under Dash0 and a GitLab group. Options marked Missing integration require the corresponding integration to be connected.
Essential Variables
These variables work in every automation, regardless of trigger type:
- {{now}}: Current timestamp (e.g.,
2026-06-13T14:30:00Z) - {{today}}: Current date (e.g.,
2026-06-13) - {{slack.channel.name}}: Slack channel where the trigger fired (Slack triggers only)
- {{slack.message.text}}: Message content (Slack message triggers only)
- {{check.name}}: Name of the failed check (check triggers only)
- {{github.repository}}: Repository name (GitHub triggers only)
- {{gitlab.project}}: Project path (GitLab triggers only)
The prompt editor shows available variables as you type. Start typing {{ to see autocomplete suggestions for the selected trigger type.
When to use parameters
Use Parameters for prompt values you define once and reuse across automation runs:
- Environment names:
{{environment}}set toproductionorstaging - Default channels:
{{alert_channel}}set toincidents - Team identifiers:
{{team}}set toplatform-team - Common timeframes:
{{default_window}}set to1h
To define a parameter:
- Navigate to Sandbox in the automation editor.
- Find Parameters and click Add parameter.
- Enter a key (e.g.,
environment) and value (e.g.,production). - Reference it in your prompt as
{{environment}}.
Parameters are stored as plain text and are visible to the model. Do not put credentials in them.
Parameters do not become shell environment variables. Use Setup variables to pass non-secret values to a setup script.
Multiple Triggers and Variables
When an automation has multiple triggers, only variables from the firing trigger are populated. Other variables remain as literal {{...}} text in the prompt.
If you mix trigger types (e.g., Slack + Schedule), handle this in your prompt:
If this is a Slack message, respond in #{{slack.channel.name}}.
If this is a scheduled run, post to #daily-reports.Alternatively, create separate automations for each trigger type to keep prompts simpler.
Advanced Variables
These variables are available but less commonly needed:
- {{dash0.dataset}}: Dataset the automation runs in
- {{dash0.workflow.id}}: Automation's ID
- {{dash0.workflow.name}}: Automation's display name
- {{dash0.workflow.version}}: Automation's version
- {{dash0.workflow.run.id}}: Unique ID for this specific run
- {{dash0.trigger.kind}}: Trigger type that fired (e.g.,
slack_bot.message)
Slack-specific:
- {{slack.channel.id}}: Slack channel ID
- {{slack.user.id}}: Slack user ID
- {{slack.team.id}}: Slack workspace ID
- {{slack.message.timestamp}}: Message timestamp
GitHub-specific:
- {{github.pull_request.number}}: PR number
- {{github.deployment.environment}}: Deployment environment
- {{github.release.tag}}: Release tag
GitLab-specific:
- {{gitlab.instance}}: Instance host the event came from
- {{gitlab.group}}: Full group path
- {{gitlab.merge_request.iid}}: Merge request IID
- {{gitlab.noteable_type}}: What a comment is on (
MergeRequest,Issue,Commit,Snippet)
Webhook-specific:
- Custom keys in a webhook's
variablesmap resolve at runtime even if the editor marks them as unknown. See Webhook Trigger for the payload format and variable precedence.
Use these when you need to reference the automation itself or track specific runs in external systems.
Troubleshooting
For common trigger issues, see:
- Automation Doesn't Trigger — Why automations don't fire when expected
- Variables Show as {{...}} — Why variables aren't resolving
- Missing Integration Warnings — Connect required integrations
Further Reading
- Write Prompts — Create effective instructions using variables
- Set Guardrails — Control what Agent0 can access
- Configure General Settings — Set up basic automation information
- Use Templates — Start with pre-built trigger configurations

