Dry-run
In the flow editor, click Test run. You get a simulation panel:- Pick a trigger event (e.g.
message_receivedon WhatsApp). - Fill in simulated message text, tags, contact fields.
- Click Run.
- which conditions matched
- what message would have been sent (not actually sent)
- which assignee would have been chosen
- any tags / actions that would have fired
Validation
When you click Publish, Keloa validates the flow and blocks publishing if:- A node is missing a required config (e.g. Message with empty template).
- A Condition has an unreachable branch.
- A WhatsApp Message is outside the 24-hour window and isn’t a template.
- The flow would loop indefinitely.
Publishing
Click Publish. The flow:- Gets a version stamp.
- Becomes live immediately — next matching trigger runs it.
- Previous version is archived (not deleted).
Monitor
Open the flow → Runs tab for a live log:- Every trigger firing (timestamp, conversation link)
- Which branch was taken at each condition
- What nodes ran
- Any error messages
Rollback
Go to Versions → pick a previous published version → Restore. It becomes live immediately. The broken version stays archived in case you want to compare or patch.Pausing
Toggle the flow’s status to paused to stop all runs without deleting. Useful during incidents or while redesigning.Best practices
- Ship small, iterate. One flow, one purpose. Don’t build a mega-flow with 30 nodes.
- Tag from the flow, so you can measure its impact later in analytics.
- Dry-run three scenarios: the happy path, an edge case, and a “nothing matches” case.
- Review runs weekly for the first month. Most surprises show up in the first 100 runs.