Test Bento Flows Before They Launch
Use Bento's built-in test suite to replay events, validate split logic, and ship automations with confidence.
Last updated: October 30, 2025
Bento ships with a flow test suite that replays events through your automation exactly the way the platform will execute them in production. Use it whenever you tweak routing logic, add new splits, or want to confirm a fix before publishing.
Open the test runner
- In the flow editor, choose Start a task → Test from the toolbar.
- Paste the event ID you want to replay. You can grab IDs from the visitor activity feed or the Events tab inside a profile.
- Click Run to simulate the event.
The canvas highlights each step as the event traverses your flow, so you can trace the path without sending live traffic.
Tip: Label your events clearly (e.g.,
order.approved) so you can spot the right sample quickly when hunting for an ID.
Catch logic mistakes early
Testing flagged a real-world regression where one branch used contains instead of equals. When an event named unapproved hit the flow, both the approved and unapproved branches fired because the string approved appears in both. Replaying the event exposed the issue immediately—no subscribers were harmed.
- Prefer
equalswhen matching exact event names. - Add guard steps (like condition checks) to stop an event from continuing if it should exit.
- Re-run the same event after every tweak to confirm the fix.
Validate splits and personalization
Need to verify a property-based split? Update the field on a test profile, re-run the flow, and confirm the visualizer reaches the correct branch. This is perfect for testing name-based splits, pricing tiers, or geographic segments without modifying production data.
- Edit the profile field, such as first name or plan code.
- Re-trigger the same event or use Replay in the visitor timeline.
- Ensure the flow lands on the expected node before rerouting live contacts.
Watch the walkthrough
Prefer video? Watch the flow testing demo to see the full setup, replay, and debugging process end to end.
Testing each branch before activating a flow keeps surprises out of customer inboxes. Lean on the suite anytime you wonder “what happens if…?” and you’ll catch regressions before they ship. Need a second pair of eyes? Drop questions in the Bento Discord and we’ll help you trace the automation together.
Need the original Markdown? Open raw file