A test run on its own gives a webhook an empty body. To build against a real request, use the Test URL: start listening, send the request, and a test run of your draft starts with exactly what was sent.
Who can do this
Workspace Admins and Editors.
Steps
Open the workflow in the designer and select the Webhook trigger.
Copy the Test URL with Copy. Use this while you build. It only works while you are listening.
Select Listen for a test event at the bottom of the panel. The button reads Starting, then Stop listening.
A toast says Listening — Send anything to the test address in the next two minutes. The trigger shows Listening for a test event… — Send anything to the test URL and a test run starts with it — what it brought is on Output.
Within two minutes, send a request to the Test URL from the other system, or from a tool such as curl or Postman, using the trigger's Method.
A toast says Test event received — It started a test run with what was sent. Follow it on the canvas. The test runs like any other; the trigger's Output shows the request.
To give up early, select Stop listening — The test address takes nothing now.
What happens next
- The first request starts the test. Listening stops after it. Listen again for another.
- The caller gets what it would get from the Production URL — 200 at once, or the workflow's answer if Respond waits — so you see what the other system will receive. At once with 200, the body is
{"received": true, "runId": "…"}. - It counts as a test run, not against the month's runs.
- It runs in the environment chosen in Test in:.
Good to know
- Two minutes. If nothing arrives, Stopped listening — Nothing arrived in two minutes. Listen again when you are ready to send.
- The Test URL is not the Production URL. Never give the Test URL to a live system.
- The same limits apply: 256 KB a request, and the trigger's Method only.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| The caller gets 404 — Nobody is listening on this test address. Press “Listen for a test event” in the designer, then send it again. | You are not listening, or the two minutes ran out, or a request already used it. | Select Listen for a test event, then send again. |
| The caller gets 405 | It used a method the trigger does not take. | Send with the trigger's Method, or change it. |
| The caller gets 409 with A test of this workflow is already running. Wait for it to finish, or stop it. | A test was already going. You are still listening. | Wait for it to end, then send again. |
| The caller gets 429 with You have used today's 50 test runs. They come back at midnight. | The workspace has used today's test runs. | Wait until midnight. |
| Listen for a test event is greyed out | A test run is going. | Wait for it to finish. |