Automation Triggers
Always-on agents start from events, schedules or explicit commands.
Use the right surface
After this you can pick Automations for the right job and define done.
Done means you can select a trigger and make the do-nothing case explicit.
Always-on agents need a clear trigger, identity, permission boundary and approval path.
Use Automations when a repeated workflow should run without a human opening Cursor. Keep the boundary narrow.
Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.
Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Run this loop in a real repo.
- Entry point
- Automations setup, Slack emoji triggers, GitHub triggers, templates and event triggers
- Source
- Automations docs and June 2026 Automations changelog
Use the source as the product reference.
Ask Cursor for an output you can inspect.
If the output cannot be checked, narrow the task before you continue.
A good run leaves a file, setting, screenshot, command result or written claim you can verify.
Takeaway. Done means you can select a trigger and make the do-nothing case explicit.
Self-check
QWhen should you reach for Automations?
Run it
After this you can do the task with clear scope and one proof point.
Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.
- 1Build all three parts of an automation: a trigger, the instruction it runs, and the tools it may use.
- 2Filter the trigger with allow-lists so only the right events, repos or authors fire it, and reach for a webhook as the universal escape hatch when no built-in trigger fits.
- 3Define the exact conditions for action and no action, especially for comments and emoji reactions.
- 4Test on a low-risk trigger before widening scope.
The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.
Keep the task small enough to review.
Trigger filtering (allow-lists, or a webhook fallback) keeps the automation from firing on noise.
Takeaway. Stop when you have proof: The trigger carries enough context from Slack, issue, PR, review thread or workflow run..
Self-check
QWhich habit makes this workflow safe to use on a real project?
Check it
After this you can find the first failed check before changing tools.
Verification decides the next move.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Pick a row to see what to look for.
Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.
No proof means more checking.
Use a real repo or admin setting. Save the prompt, context and proof.
Takeaway. If it fails, find the first failed check.
Self-check
QThe workflow failed. What is the best first move?