Automation rules

Goal

Create event-driven rules that run safe actions only — notify, set field, tag, create draft, or require approval. Automation never auto-posts or pays.

Who it is for

Users with automation.view / automation.manage. Tenant admins with automation.admin own Automation setup (limits and trigger-type catalog).

Preconditions

• Module automation enabled.
• Trigger types / limits configured under Administration → Automation setup when you need custom catalogs or higher rule caps.

Steps — rules

1. Open Administration → Automation.
2. Choose New (automation.manage) or edit a row.
3. Set Name, Event, optional Conditions (field / op / value; ops include eq, ne, gt, gte, lt, lte, contains, in, exists).
4. Add Actions from the safe list only: notify, set_field, tag, create_draft, require_approval. Action params are JSON.
5. Toggle Active, Save. Open Runs on a rule to inspect execution history.

Steps — setup (automation.admin)

1. Open Administration → Automation setup.
2. Set max rules, run retention days, max runs per hour, and whether only safe actions are allowed.
3. Maintain Trigger types catalog as needed.

Result

Matching events enqueue runs under the configured limits. Unsafe action types are rejected.

Hard stops

Symptom	Cause	What to do
Action not permitted	Type outside safe whitelist	Use only notify / set_field / tag / create_draft / require_approval
Rule limit reached	Tenant max rules hit	Deactivate unused rules or raise limit in Automation setup
422 on params	Invalid JSON / missing fields	Fix paramsText and required condition fields

Related

• Approval policies
• Integrations