Automations
Triggers and actions
The events you can react to and the actions an automation can run.
Every automation pairs a trigger (the event that starts it) with one or more actions (what happens in response). This page lists what's available so you can picture the rules you want to build.
In this article
Triggers
A trigger is the event Cadence watches for:
- Sermon created — a new sermon is added.
- Sermon status changed — a sermon moves to Review, Finalized, Delivered, and so on.
- Task created — a new task is added.
- Task status changed — a task moves between statuses.
- Approval requested — someone submits something for sign-off (such as a purchase request).
- Delivery approaching — a scheduled sermon delivery is coming up on the calendar.
Actions
An action is what runs when the trigger fires:
- Create a task — with a title, assignee, and due date.
- Update a status — move a sermon or task along its workflow.
- Notify someone — send a notification to a person or team.
- Request an approval — route something for sign-off.
- Stamp an asset pack — attach a standard set of deliverables to the item.
Useful pairings
A few rules teams set up often:
- Sermon status → Review creates a task for the tech team to build slides.
- Delivery approaching notifies the worship and tech teams.
- Approval requested requests an approval from the right budget owner.
Automations act on real data the moment they're enabled. Test a new rule on a low-stakes item before turning it loose on everything.