Test Flow

The Test Flow dialog lets you run the version you are editing on a real channel — WhatsApp, Web or Email — without touching the published version, and tells you beforehand which nodes that channel cannot run.

Accessing Test Flow

Click the Test Flow button in the top bar to open the dialog, titled Probar el bot. The same dialog opens in share mode (Compartir el bot) from the bot links of a connector; the difference is the version it points at, see below.

Channel compatibility

As soon as you pick a channel, the dialog walks the flow you are viewing and every flow it chains into through Jump To nodes (each flow is visited once, even if two flows jump into each other) and compares every node type against what the channel supports.

If any is found, a warning appears in the dialog: Nodos incompatibles con el canal {channel} — "Este flujo, o alguno de los flujos que encadena, usa nodos que el canal {channel} no soporta." — followed by the affected flows, the incompatible node types and the instruction to remove them. The action buttons of the dialog (create the test conversation, copy or open the web link) are disabled until you do, and the hint under the link reads "Corregí los nodos incompatibles para poder usar el canal {channel}."

Testing Channels

WhatsApp

1. Click Test Flow
2. Select WhatsApp as the channel
3. Under Responde desde, choose the connector (the Business number the bot answers from)
4. Enter the phone number of the person who will talk to the bot, with country code
5. Click Crear conversación de prueba, then scan the QR code, open WhatsApp from the link or copy the link

The bot is assigned to that contact, and the conversation runs the draft version you are editing.

Web

1. Click Test Flow
2. Select Web as the channel
3. Click Probar to open the link in a new tab, or Copiar to copy it

The test link opens the version you are editing without touching the published one:

{domain}/{tenant}/{alias}?version={v}&status={s}

• version - the specific version being tested
• status - the flow status (draft, active)

The Preview button in the top bar opens this same link directly.

Email

1. Click Test Flow
2. Select Email as the channel
3. Under Responde desde, choose the email connector
4. Enter the email address that will talk to the bot
5. Click Crear conversación de prueba

The conversation is created and waits: "La conversación fue creada. Enviá un correo para iniciar el flujo." Send an email from that address to the connector's address and the flow starts.

Share mode

Opened from a connector's bot links, the dialog reads Compartir el bot and always points at the active version: the web link has no version parameters, and on WhatsApp it generates a QR anyone can scan to start a conversation with the published bot. The compatibility check runs the same way.

What you see while testing

A test conversation is a real conversation on the channel, so everything the engine records is available to you:

• Notices. Any trouble the bot runs into — a node that fails, a variable nobody set, a file the node could not read — is left as a notice on the conversation. Open it in Chat to read them on the conversation, or find them aggregated in Flow Notices; both link back to the node in the editor.
• Jump To, Human Takeover and End are not failures. A flow that hands off to another flow, to an agent, or simply ends is doing what you designed; none of them leaves an error notice.
• Files on the web channel are limited to 20 MB each and to the accepted extensions (pdf, csv, doc, docx, xls, xlsx, jpg, jpeg, png, mp4, json, zip, heic, heif, webp, txt); the portal refuses anything else before uploading. See Customer Portal.
• A message WhatsApp rejects while you test — the 24-hour window is closed, Meta's frequency cap for that user was hit, the template is paused — shows up as a notice explaining the reason in Spanish and what to do about it, instead of a bare provider code.
• An unresolved variable reaches you as {{name}} in the message, plus a warning notice naming it. No stand-in text is sent.

The error panel

The error panel at the bottom of the canvas belongs to the editor, not to the dialog: it lists what the publish gate found on the flow.

For each entry you can click Fix with AI to have the AI assistant suggest a solution, or Fix All with AI to address everything at once.

Best Practices

Before Testing

• Pick the channel you will actually deploy on and read the compatibility warning if one appears
• Ensure all required node configurations are complete
• Check that variables are properly declared and written by some node
• Verify conditional logic paths

During Testing

• Test all possible user paths
• Try edge cases (invalid inputs, unexpected responses, a file of the wrong type)
• Verify variable values are captured correctly
• Keep the conversation open in Chat to read notices as they appear

After Testing

• Review any unexpected behavior and the notices it left
• Check the flow from start to end
• Test on actual devices (mobile, desktop) for web flows

Troubleshooting

Validation errors persist

If errors don't clear after fixing:

• Wait for the autosave, or refresh the page
• Check if the fix was actually applied to the right node — the panel names the node

Test URL doesn't work

Check that:

• The alias is correctly configured
• Your account has permission to access test URLs
• No incompatible node is disabling the buttons

WhatsApp test not received

Verify:

• The phone number includes country code
• The connector is correctly configured and active
• The notices of the conversation in Chat: a rejection by Meta is explained there

Web preview shows wrong content

• Clear browser cache
• Ensure you're using the correct version parameter
• Check if web configuration is properly saved