Test it, see every version, read every run
Free for 7 days, no credit card required
Try a flow on your own phone before anyone else gets it, go back to any save with what changed marked on the canvas, and read each run step by step, with a retry when something failed.
- Meta's official API, no password, nothing installed
- Unlimited contacts on every plan
- AI replies in your customer's language
- From $29 a month
Ship a flow without guessing
The four checks a careful builder runs, each one on the canvas.
- 01
Test on your phone
Scan the QR code: your chat with the page opens and the saved version runs for you alone, even while the flow is off.
The link works for 30 minutes and can be renewed
- 02
Fix what it finds
The bar counts the things to fix, each one a click away, and says Ready to go live when there are none.
A paused flow saves as a draft with its problems
- 03
Tidy up
One press lays the flow out in your direction: left to right, or top to bottom. It moves cards, never what the flow does.
The same flow always tidies to the same picture
- 04
Watch the numbers
Insights put the counts on the canvas: who started, finished, waits, went to your team or failed, and each step’s reach.
Last 7 days, last 30 days or all time
Why it happened, step by step
Every run keeps its path and the reason behind each step, so “why didn’t she get the code?” has an answer in one click.
- What each rule read
- A condition’s run shows every rule with its verdict, and Not checked when the answer was already decided.
- What Meta said
- A refused message names the reason: the 24-hour window, a sending limit, a page to reconnect.
- Retry from failed step
- Fixed the endpoint or reconnected the page? The run picks up where it stopped.
RunsEvery run still going, and the last 50 finished
AllFailedStill goingWith your teamFinishedSkipped
lucia.mxFailed · 10:42 · took 2 s
CommentedLINK please 🙌 · on the new roast reel
ConditionEvery rule had to match · Follows you: Matched · Has an email: Matched · Went on by Yes
MessageSent
HTTP requestThe API call failed · Answered 503 in 1,204 ms
Retry from the step that failed?The run continues for lucia.mx on the version it started with. Steps that already went are not sent again.
Keep as failedRetry nowEvery tool, in the builder’s words
The labels you will see in the app, what each one does, and the rule behind it.
Testing
Before anyone else sees it.
- Test on your phoneA private test link
A QR code and a link open your own chat with the page and run the saved version for you only. Nobody else gets anything, live or not.
The link works for 30 minutes; New link makes another.
- Comment flows: comment yourself
A flow that starts on a comment is tested by commenting on your post from your own account; test links are for flows that start in the chat.
- Ready to go liveProblems counted before it goes live
Paused, a flow saves as a draft with its problems listed; going live refuses them, and checks the page’s connection has the permissions the flow needs.
- Edits never land mid-run
A run keeps the version of the flow it started on, so changing a live flow never changes a conversation already under way.
Versions
Every save, kept.
- VersionsEvery save is a version
Each save that changed something keeps the whole flow, who saved it, whether it was live, and what changed: steps added, removed or changed, wires, the start, settings, moves.
Named versions are kept for good, plus the last 100 saves.
- RestoreGo back without losing anything
Restore puts a version on the canvas as unsaved changes; nothing goes live until you save, and Cmd+Z takes it back. Or copy it as a new flow, paused.
- Name this versionMark the ones that matter
Name a version with a note, like “Before the summer sale”, and filter the list to named ones.
- A tidy-up reads as moved
Moving cards is its own kind of change, so a tidy-up never looks like an edit in the list.
Runs
What happened to each person, and why.
- HistoryEvery run, step by step
Each run shows every step with why it did what it did: what each condition rule read, which way it took, what was sent, what Meta refused.
Every run still going, and the last 50 finished in full.
- Show runsFilters for what matters
All, Failed, Still going, With your team, Finished, Skipped. Runs still going are listed first, with when each continues.
- Retry from failed stepMend a failure in one press
A failed run walks again from the step it stopped on, on the version it started with; what already went is not sent again.
Offered for failures a second try can fix: an endpoint, Meta’s limits, a reconnected page. Never for a closed window.
- InsightsCounts on every step
Reached, sent, tapped or opened and stopped here per step; opens per link; a step added later counts only from its day.
Test on your phone, in the app
Scan the code with your phone: it opens your chat with northwind.coffee, and the saved version runs for you only, even while the flow is off.
- Copy link
- The same test as a link, for the phone in your hand.
- 30 minutes
- The link works for half an hour; make a new one any time.
Every save, newest first
The Tasting bookings flow’s versions: the one live now, the saves before it with who saved them, and what changed.
- Live now
- The version people get.
- Named
- Named versions are kept for good, with the last 100 saves.
Numbers on every step
Insights over the last 30 days: 47 started, 12 finished, 1 waiting and 34 with your team, and on each step how many it sent and who tapped.
- Last 7 days, Last 30 days, All time
- One switch for the whole canvas.
- Per step
- Sent, clicked, and each way taken.
The numbers behind it
What the builder keeps, and for how long.
| What | The limit | Set by |
|---|---|---|
| Test link | Works for 30 minutes, for you only, renewable | CommentWatchDog |
| Versions kept | Every named one, plus the last 100 saves | CommentWatchDog |
| Runs in history | Every run still going, and the last 50 finished in full | CommentWatchDog |
| Insights ranges | Last 7 days, last 30 days, all time | CommentWatchDog |
| Steps in one flow | Up to 60 | CommentWatchDog |
| Retry | From the failed step, on the version the run started with | CommentWatchDog |
All numbers are the flow builder’s own; Meta sets none of them.
Questions about testing and versions
What people ask before they put a flow live.
Yes. Test on your phone gives a QR code and a link that open your own chat with the page and run the saved version for you only, even while the flow is off; nobody else gets anything. The link lasts 30 minutes. A flow that starts on a comment is tested by commenting on your post from your own account.
Yes. Every save is a version: open one, see what changed since, and Restore it onto the canvas as unsaved changes, or copy it as a new paused flow. Named versions are kept for good, plus the last 100 saves.
Open the flow’s history and the run: each step says what it did and why, from what each condition rule read to the reason Meta refused a message, like a closed 24-hour window.
Yes, when a second try can fix it: Retry from failed step walks the run again from the step that failed, on the version it started with, and never sends again what already went. A closed window is not retried.
Turn on Insights: every step shows how many reached it, were sent it, tapped or opened something and stopped there, every link how many opened it, over the last 7 days, 30 days or all time. Paths of an A/B split are counted the same way.
It lays the whole flow out in one press, in the direction you chose under Layout: left to right (right to left when the app is in Arabic) or top to bottom. A wire that skips a column gets its own lane, wires back to earlier steps run around the cards, and unconnected steps are gathered apart. It only moves cards, and the same flow always tidies to the same picture. Build with AI and templates use the same layout.