Service Schedule + Automation Rules
Quick Start
Open the Schedule tab and create a service window (e.g., Sunday 8:00 AM - 12:30 PM)
Add an automation rule — pick a trigger (time, event, or manual) and an action
Run a dry test to verify timing
Enable the rule for the next service
Who This Is For
Teams with repeatable weekend workflows that want to automate routine actions.
What You Will Accomplish
Create service time windows by day and time
Build automation rules with triggers and actions
Test rules safely before using them in a live service
Prerequisites
Step-by-Step Setup
Go to the schedule/automation section in the portal.
Set up your service times by day and time (e.g., Sunday 8:00 AM - 12:30 PM).
Create rules by choosing a trigger:
Timer — runs at a specific time during the service window
Event trigger — runs when something happens (like a device disconnecting)
Manual trigger — runs when you press a button
Add one or more actions to each rule. Set the order and add delays between actions.
Important: Always add delays between restart actions and device commands. Equipment needs time to boot up before it can accept new instructions.
Save the rule and run a test for one service window to make sure the timing and actions are correct.
Validation Checklist
Common Issues and Fixes
| Symptom | Cause | Fix |
|---|---|---|
| Actions run at the wrong time | Timezone mismatch | Check that your church timezone in settings matches your actual timezone |
| Rule never fires | Trigger condition never happens | Make sure the triggering event actually occurs during the service window |
| Rule fires over and over | No safety limit set | Add a "once per window" or cooldown limit to the rule |
| Actions happen too fast | No delays between steps | Add 5-15 second delays between actions so equipment can keep up |
Rollback / Fallback
Pause all automation rules.
Run things manually for the next service.
Re-enable rules one at a time after testing each one.