Automation Builder
Create event-driven automation rules using a step-by-step workflow builder -- choose a trigger, add conditions, pick an action, and configure the details.
The Automation Builder (/automations/builder) is a guided workflow for creating automation rules. It walks you through five steps: Trigger, Conditions, Action, Configure, and Review.
Quick templates
When you open the builder, a Quick Templates gallery appears on the first step. Templates are pre-configured workflows covering common use cases. Selecting a template pre-fills all five steps and jumps you directly to the Review step, where you can adjust the name and save.
Step 1: Choose a trigger
Select the engineering event that should start the workflow. Available triggers include:
| Trigger | When it fires |
|---|---|
HIGH_RISK_PR | A PR's deploy risk score reaches HIGH or CRITICAL |
DEPLOY_COMPLETED | A deployment finishes successfully |
DEPLOY_FAILED | A deployment fails |
PR_MERGED | A pull request is merged |
PR_OPENED | A new pull request is opened |
COVERAGE_REGRESSION | A merged PR drops test coverage below a threshold |
CYCLE_TIME_EXCEEDED | PR cycle time exceeds your configured threshold |
REVIEW_TIME_EXCEEDED | Time to first review exceeds your configured threshold |
INCIDENT_OPENED | A new incident is created |
SCORECARD_BELOW_THRESHOLD | A scorecard score drops below a target |
SCORECARD_ABOVE_THRESHOLD | A scorecard score exceeds a target |
INITIATIVE_OVERDUE | An initiative passes its target date |
Each trigger card shows its icon and a short description. Click a trigger to select it, then click Next.
Step 2: Add conditions (optional)
Conditions let you narrow when the action fires. If you skip this step, the action runs on every trigger occurrence.
Each condition has three parts:
- Field -- a data field from the trigger (e.g., risk score, repository name, cycle time)
- Operator -- comparison operator (equals, greater than, less than, contains, etc.)
- Value -- the threshold or match value
Fields are typed: select fields show a dropdown, number fields accept numeric input, and boolean fields show a true/false toggle.
You can add multiple conditions. All conditions must be met (AND logic) for the action to fire. Click Add Condition to add another row, or click the trash icon to remove one.
Step 3: Choose an action
Select what happens when the trigger fires and conditions are met:
| Action | What it does |
|---|---|
| Slack Notification | Posts a message to a Slack channel |
| Jira Status Transition | Transitions a Jira issue to a new status |
| Create Jira Issue | Creates a new Jira issue |
| Create Linear Issue | Creates a new Linear issue |
| Fire Webhook | Sends a POST request to a URL |
| Email Notification | Sends an email notification |
| Update Initiative | Updates an initiative's status or progress |
Step 4: Configure the action
Each action has its own configuration parameters. For example, the Slack Notification action asks for a channel and message template. Required fields are marked with a red asterisk.
Use {{fieldName}} syntax in text fields to insert trigger data dynamically. For instance, a Slack message for the HIGH_RISK_PR trigger might include {{prTitle}}, {{riskScore}}, or {{repository}}.
Step 5: Review and name
Give the workflow a name (required) and an optional description. The review step shows a visual summary of the complete workflow:
- When -- the selected trigger
- If -- any conditions (shown only if conditions were added)
- Then -- the selected action and its configured parameters
Click Create Workflow to save. The rule activates immediately and appears on the Automations list page.
Automation list and logs
After creation, the rule appears at /automations. Each rule card shows:
- Name, trigger, and action as badges
- Active or disabled status (toggle with the power icon)
- Last triggered timestamp and total execution count
- Log count
Switch to the Activity Log tab to see every execution with status (SUCCESS, FAILURE, or WARNING), the rule that fired, any error messages, and timestamps.