Skip to main content
In Automations → Conversation started → Test, choose a Test source. Samples use that connection’s assistant and widget pre-chat form, including configured custom fields and variable examples. A messaging-channel start contains its channel identity fields; it does not invent widget form fields or variables absent from that event. Select Start live test, then Open test chat for a widget. Complete the form and continue. For a messaging channel, start a new conversation there. Messages in an existing conversation do not produce a new start event. The listener waits for up to two minutes and displays the first matching new conversation. You can stop it at any time. Switch between Fields and JSON. Click a field path to copy its template variable, or use Copy JSON. Changing trigger filters clears earlier test data. Samples are synthetic; only live capture shows actual received values. Listening reads data only and works with draft or paused automations. A real chat still uses normal credits and can trigger active automations. Pause any workflow you do not want to execute before starting a real chat.

​
REST / MCP

POST /api/v1/automations/trigger-test-data · get_automation_trigger_test_data
Use mode: "listen" without since to arm the listener. Keep the returned server since value and pass it with source_id on subsequent polls. payload: null means no matching new conversation yet. Stop polling after two minutes; timestamps older than ten minutes are rejected. Select a source from sources when multiple channels match. No automation ID or activation is required.