Who this is for: Teams explaining automation in their own software.
What to prepare
- Rule-builder screenshots
- Trigger and condition definitions
- Saved configuration
- Observed matching-event result
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–7s
Name the rule’s job
Show the sample workspace and the narrow routing task.
On screen:Route a design request to its reviewer
- 02
7–17s
Choose the trigger
Show the actual submitted-request trigger and state any setup requirements.
On screen:When a request is submitted
- 03
17–27s
Set the condition
Select Category equals Design using supplied controls and exact labels.
On screen:If Category is Design
- 04
27–37s
Choose the action
Set Assign Example reviewer through the verified action selector.
On screen:Assign Example reviewer
- 05
37–44s
Save configuration
Perform the actual save or enable step and hold the configured-state indicator.
On screen:Rule configured
- 06
44–54s
Inspect a matching event
Show fictional R-053 submitted with Category: Design and its observed resulting owner.
On screen:One matching sample event
- 07
54–60s
State the bounded result
Hold source category and destination owner together or in a labeled comparison.
On screen:This sample request received the configured owner
Make it your own
- Trigger and condition
- Use the documented event and a clear field-value match.
- Configured action
- Supply a supported action, setup requirements and the real save or enable step.
- Example execution evidence
- Use an observed matching event and result, or label the ending as expected behavior rather than a completed run.
Prepare rule evidence
Supply the trigger definition, condition type, action behavior and execution evidence. If only configuration is available, change the final scenes to a clearly labeled expected-behavior explanation. Do not manufacture a successful run.
Adapt the logic
Use a different supported condition only when the sample event makes the match obvious. A 30-second version can start with a saved rule, but must identify that prerequisite. Keep a nonmatching event for a separate training example when runtime is tight.
Review the capability boundary
This storyboard describes the reader’s product; it does not assert Animro automation or integrations. Distinguish configured intent, execution and confirmed result. Avoid claims about guaranteed routing, universal compatibility or execution speed.
Review checklist
- Trigger, condition and action are distinct.
- Configured and executed states are not conflated.
- The example event satisfies the condition.