12 min
React to GitHub events
Start a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.
5,000 free credits to start.
- 01
Connect GitHub and choose the repositories
Connect GitHub from Settings, then Integrations, and select which repositories the connection covers. That selection is the limit of what a workflow can reach. Start with one repository.
- 02
Pick the event that matches the task
A reviewer runs on `pull_request.opened` and `pull_request.synchronize`. A build explainer runs on `workflow_run.completed`. A release notes writer runs on `tag.created`. An issue triager runs on `issues.opened`. GitHub exposes twelve events.
- 03
Filter the trigger down
Filters combine with AND or OR and accept globs. Filter by base branch so the workflow ignores long-lived feature branches. Filter by label so a pull request opts in one at a time.
- 04
Write the prompt against the event payload
The run receives the event that started it, so the prompt can refer to the pull request, the workflow run, or the tag directly. Tell it what to read first. The diff, the contributing guide, the last twenty merged reviews.
- 05
Start with a label filter and a comment
Have the agent post a comment instead of an approving review, and gate it behind a label. Add the label to a few of your own pull requests, read what it wrote, then widen the filter.
- 06
Decide who can change it
A workflow that comments on pull requests is one your team will read closely. Editors and admins change the prompt. Operators run it. Viewers read the runs. Share it with the team that owns the repository.
Keep going
Next guides
10 min
Run your first workflow
Describe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.
8 min
Put a workflow on a schedule
Turn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.
9 min
Share with your team
Hand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.
Templates
Put it to work
Templates that use what this guide covers.
Engineering
Pull request reviewer
Reviews every pull request against your conventions and leaves inline comments only where it found something concrete.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.
Engineering
Incident postmortem drafter
Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.
Try it in your workspace.
Start free, connect a tool, and write the first prompt in plain words.