What is a Workflow?A Workflow automatically runs an Agent on a repository when:
- A schedule is reached (cron)
- An event occurs (webhook, e.g. GitHub PR)
- Daily vulnerability scans
- Weekly changelog generation
- Reacting to new pull requests or Sentry alerts
Creating a Workflow
Start from scratch or a template
In Mission Control → Workflows, create a new workflow.
Start with a Blank Workflow
Start with a Blank Workflow
Create a workflow from scratch by clicking Create Workflow.
You’ll choose the repository, agent, trigger type, and schedule or webhook.
You’ll choose the repository, agent, trigger type, and schedule or webhook.
Use a Workflow Template
Use a Workflow Template
Select any of the “Try these Workflows” cards such as:
- Update agents.md
- Draft Changelog Updates
- Solve Snyk Vulnerabilities
Name the Workflow
Give your Workflow a clear, descriptive name.Examples:
Morning status checkWeekly changelog draftDaily Snyk vulnerability scan
Select Repository & Agent
Choose:
- Repository – the codebase the Agent will run against
- Agent – the configured Agent (model, rules, tools, prompt) that should perform the work
Choose Trigger Type
Pick how this Workflow should run:
- Cron – run on a schedule (daily, weekly, hourly, custom)
- GitHub – run when GitHub events occur (PR opened, merged, issue opened, label added)
- Webhook – run when an external system sends a request
Configure the Trigger
Cron Workflow
Cron Workflow
For scheduled Workflows:
- Select Cron as the trigger type
- Choose a schedule:
- Common presets (e.g. weekdays at 9 AM UTC)
- Hourly, Daily, Weekly, Monthly
- Or define a Custom expression
- (Optional) Add additional instructions for this Workflow run in the text area.
- Run a morning status check on your repo every weekday
- Refactor React components once per week
- Generate a weekly changelog from recent commits
GitHub Trigger Workflow
GitHub Trigger Workflow
For GitHub event-based Workflows:
When using the “PR opened” event type, enable Re-run on new commits to send a follow-up message to the active agent session whenever new commits are pushed to the PR. The agent receives commit details (SHA, message, author) and can continue working on the updated code without creating a duplicate session.Example use cases:
- Select GitHub as the trigger type
- Choose your connected GitHub App installation
- Select the event type:
- PR opened – triggers when a pull request is opened
- PR merged – triggers when a pull request is merged
- Issue opened – triggers when an issue is created
- Label added – triggers when a specific label is added to a PR or issue
When using the “PR opened” event type, enable Re-run on new commits to send a follow-up message to the active agent session whenever new commits are pushed to the PR. The agent receives commit details (SHA, message, author) and can continue working on the updated code without creating a duplicate session.Example use cases:
- Run an Agent on every new pull request for automated review
- Trigger code quality checks when PRs are opened
- Keep agents updated on PR changes with the re-run option
Webhook Workflow
Webhook Workflow
For custom webhook-based Workflows:
- Select Webhook as the trigger type
- (Optional) Set a Secret Header (e.g.
X-Webhook-Secret) - (Optional) Set a Secret Value (token your external system must send)
- CI/CD pipelines
- Any external system that can send HTTP requests
- Kick off a workflow when Snyk or Sentry detects an issue
- Integrate with custom internal tools
Monitoring Workflow Runs
Workflow runs show up just like Tasks:- Each execution creates a Session
- Workflows appear in your Inbox
- You can open the detail view to see the summary, diff, and logs.