Conditions & Wait
Use conditions to target specific scenarios and the Wait node to delay actions inside one flow.
Conditions control whether a flow’s actions should run.
Examples of conditions:
- Location
- Assigned user
- Who created the event
- Whether a consent form exists
- Whether ink has been registered
Conditions Are Evaluated At Runtime
Conditions are evaluated at runtime, not at scheduling time.
This means:
- The latest data is always used
- Changes made after creation (for example location or assignee changes) are respected when the flow runs
Wait Node (Flow Control)
The Wait node adds a delay between actions.
Example:
- Send confirmation
- Wait 24 hours
- Send reminder
This lets a single flow span time without needing multiple separate flows.