Automations
Set up if-this-then-that rules so routine work happens on its own.
Automations take care of the repetitive hand-offs in your workflow. Each automation is a simple rule: when something happens (a trigger), then do something (an action). For example — when a sermon moves to "Ready for review," create a task for the tech team.
Automations are managed by administrators on church organizations with the automation feature enabled. If you don't see Automations in your sidebar, it may not be available on your plan.
In this article
How an automation works
Every automation has two halves:
- A trigger — the event that starts it. Triggers include things like a sermon being created or changing status, a task being created, or an approval being requested.
- An action — what happens in response. Actions include creating a task, updating a status, notifying someone, or requesting an approval.
You can read the full list in Triggers and actions.
Build your first automation
Create a new automation and choose a trigger — for example, "Sermon status changed to Ready."
Save and enable it. From now on, the action runs automatically whenever the trigger fires.
Test a new automation on a low-stakes item first. Automations act on real data the moment they're enabled.
Approval workflows
A common use of automations is routing something for sign-off — a purchase request, a sermon, or a project step. See Approval workflows.