Team operations
Create an operations automation
Connect a business event with the actions it should trigger.
Before you start
Rule editing requires the appropriate administrative permissions. Publishing can trigger real actions.
Step by step
- Open Automations and create a rule with a descriptive name.
- Choose the trigger: the event that starts the rule.
- Add conditions to control when it continues and review each branch.
- Configure actions, recipients, and data. Check any message or access change.
- Save the draft and review the full flow before publishing or activating it.
- Use History to review executions and their outcomes.
Plan the rule before enabling it
A trigger answers “when does it start,” a condition answers “in which cases,” and an action answers “what happens.” Write down these three decisions first. If the flow branches, review both outcomes of the condition rather than only the path you expect most often.
Action data must match the event the rule receives. Check recipients, programs, and products before enabling access changes or communications. History distinguishes completed, skipped, and failed runs. A saved draft does not prove that a rule executed. The troubleshooting guide explains how to find the part that needs attention.
What to expect
The rule defines its trigger, conditions, and actions.
Troubleshooting
Do not activate a rule just to inspect its layout. Review the specific execution error before repeating an action that might send messages or change access.