Automations

Automations perform repeated studio tasks from bounded templates. They are separate from an assistant connection: an assistant may configure a rule only within its scopes, while Stenz controls when and how the rule runs.

Safe setup sequence

1. Choose a supported trigger and template.
2. Define bounded filters, timezone, quiet hours, and rate limits.
3. Create the rule disabled.
4. Run a simulation and review candidate counts and skipped reasons.
5. Confirm the exact rule change before enabling it.
6. Monitor the first runs and pause the rule if results differ from expectations.

A simulation never sends a message, creates a booking, charges a payment, issues an invoice, or approves its own work. It is a preview of eligible items under the current data and policy.

Guardrails

Rules use idempotency and run limits to reduce duplicates. Repeated failures can auto-pause a rule. Permission loss, subscription changes, or a policy update may require reauthorization before the next effect.

Automations cannot approve their own high-risk financial, legal, or destructive action. An R3 action still needs a recent human approval in Stenz.

Tip

Start with a narrow audience and a read-only or simulated run. Expand only after the activity history matches your intent.

See Permissions and approvals for R0–R3 behavior.