Quick Start — Test Your Webhook in 2 Minutes
🚀 Want to verify your webhook before going live?
Open your agent → Webhooks tab → find your webhook
Click the three-dot menu → Send Test Webhook
Check the Overview tab in the modal — HTTP Status should show 200
If it shows 200, your webhook is working. If not, check the Common Issues below.
Why Test Before Going Live?
A webhook that is misconfigured will silently drop call data — no error in Romulus, no data in your automation. Testing before real calls arrive is the only way to confirm the connection works end to end.
How to Send a Test
Open the agent the webhook is configured on.
Click the Webhooks tab.
Find the webhook in the table.
Click the three-dot menu on that row.
Select Send Test Webhook.
The Test Webhook modal opens automatically.
Reading the Test Results
Overview Tab — Did it work?
Check two things:
Endpoint URL — confirms the destination the payload was sent to
HTTP Status — 200 means success. Anything else means a problem on the receiving end.
Use Send Again to resend without closing the modal.
Request Tab — What was sent
Shows the exact JSON payload sent to your endpoint. This is what your automation receives on every real call. Review it to confirm the data structure matches what your workflow expects.
Response Tab — What came back
Shows the response your endpoint returned. A working endpoint returns 200 OK. If it returns an error code, check your webhook URL and endpoint configuration.
Raw Data Tab — Full transaction
Shows the complete raw JSON transaction — request and response combined. Useful for deep debugging or building a custom webhook receiver.
Common Issues
HTTP Status is not 200
Your endpoint URL may be wrong, or your automation is not listening. Verify the URL in the webhook settings and check that your n8n/Make/Zapier workflow is active and the webhook node is enabled.
No response received — the modal shows an error
The endpoint timed out. Check if your automation server is running. For n8n, make sure the workflow is active. For Make, check that the scenario is active.
The data structure in the Request tab is different from what my workflow expects
Update your workflow's field mapping to match the Romulus payload structure shown in the Request tab.
Related Articles
What Are Webhooks and How to Set One Up
How to Send Call Data to a Webhook from the Calls Tab