Run a flow with nobody on the other end
POST/api/flows/:flow/test
The honest replacement for an editor "test" button that used to run a
setTimeout and print a hardcoded 200 OK with a plausible order id —
no request, no server, not even a look at the node's own configuration.
It is the SAME runner, the same handlers and the same trace recorder; only the sink differs. Nothing is sent, no contact or conversation is created, no assignment / tag / handover is applied, and the flow's analytics counters do not move.
A rest_api node DOES make its call. Not calling would remove the one
thing anybody tests a request node for — that the address, credentials
and response shape are right. What a test does not do is write the
answer back onto a real person.
answers are the visitor's replies in order; the walk stops when it runs
out of them, and stopped_for_answers says so — without it, "my test ran
out" and "the flow stopped" look identical.
The run is recorded with mode: test and returned inline. It is
excluded from GET /api/flows/{flow}/runs, which answers "what happened
to my customers".
Request
Responses
- 200
- 401
- 403
- 404
- 422
The transcript, the actions it would have taken, and the trace.
Not authenticated. code: account_disabled means the member's seat was deactivated in this workspace: the session is over even though the token was not revoked (clients sign out and clean up).
Authenticated but not allowed.
Resource not found (or not visible to the current tenant).
The request failed validation.