Automations
Run Droid on a schedule, from Slack messages, on GitHub events, or from webhooks, and pick the workflow guide that matches your job.
Automations start a Droid session every time a trigger fires, so recurring engineering work runs without someone kicking it off. Open Automations in the Factory App to create and manage them.
Triggers
| Trigger | Starts a run when | Typical use |
|---|---|---|
| Scheduled | A cron-style schedule comes due. | Triage queues, daily digests, maintenance sweeps. |
| Slack | A message lands in a channel you select. | Incident alerts, bug reports, channel Q&A. |
| GitHub | A repository event fires, such as a pull request or push. Runs in GitHub Actions. | Code review, QA, security audits, AutoWiki refresh. |
| Webhook | Another service sends an HTTP POST to the automation's URL. Available when webhook triggers are enabled for your organization. | Alert responders, CI failure triage, issue investigation. |
Where to start
Select New automation to open the marketplace. Every option lands in the same automation model: a trigger, instructions, a run identity, and a place to run.
StartersReady-made jobs such as Ticket to PR, PR Reviewer, and Error Triage with the prompt and trigger filled in. See popular use cases.
Guided setupsBuilt-in automations with a setup form for one job, such as Triage, Code Review, QA, AutoWiki, Security Audit, and Incident Response. See guided setups.
Start from scratchPick a trigger type and write the prompt yourself. See Custom Automations.
Create with DroidDescribe the job in your own words and let Droid draft the automation. See Create with Droid.
To drive GitHub automations from your own CI, use the CI Automations API.
Guided setups
Each guided setup runs a built-in skill on a trigger. The same skill also runs on demand in any Droid session. Each guide covers both, plus configuration and tuning.
Investigate alerts posted in incident channels and run root-cause analysis.