Who This Is For / When to Use
This guide is for advanced Kyrios users, developers, or automation builders who need to inspect raw webhook requests, validate payload structure, or troubleshoot webhook failures during custom integrations.
Why Use Webhook.site for Testing Webhooks
Webhook.site provides a temporary endpoint that captures incoming HTTP requests in real time, allowing users to view headers, payloads, and request methods without affecting live Kyrios workflows.
Webhook.site is useful when:
A webhook is firing but data is not behaving as expected
Payload structure needs validation before connecting to Kyrios
A third‑party tool (Zapier, Make, custom app) needs debugging
Step 1: Generate a Testing Webhook URL
Webhook.site creates a unique testing URL that captures all incoming webhook requests.
Visit Webhook.site in a browser.
Copy the Your unique URL using the Copy to clipboard button.
⚠️ Always copy the URL from the page, not the browser address bar.
Step 2: Configure the Webhook in Your Integration Tool
Your webhook‑sending tool must temporarily point to the Webhook.site URL instead of Kyrios.
Open the integration or automation tool triggering the webhook.
Locate the webhook or custom request action.
Replace the existing API URL with the Webhook.site URL.
Ensure the HTTP method (POST/GET) matches the expected behavior.
Step 3: Trigger the Webhook Event
The webhook must be triggered to send data to Webhook.site.
Trigger the event that normally fires the webhook, such as:
Submitting a form
Creating a contact
Completing a workflow step
Webhook.site logs the request instantly without requiring a page refresh.
Step 4: Review the Captured Webhook Payload
Webhook.site displays the full request details, including headers and body content.
Select the most recent request in the request list.
View the Raw Content section to inspect JSON payload data.
Enable Format JSON for easier readability.
Step 5: Copy Payload Data for Troubleshooting
Captured payload data can be shared for debugging or validation.
Click the Copy button in the Raw Content panel.
Paste the data into documentation, developer notes, or a support request.
What to Do if the Webhook Is Not Firing
If no data appears in Webhook.site, the webhook is not being triggered.
Check the following:
The webhook action is enabled
The correct HTTP method is selected
Required headers or authentication tokens are present
The triggering event is actually firing
Using Webhook.site With Kyrios Workflows
Webhook.site should only be used for testing and debugging.
After validation:
Replace the Webhook.site URL with the Kyrios endpoint.
Save the integration or workflow.
Run a live test to confirm behavior.
Webhook.site URLs should never remain in production workflows.
Security and Data Safety Notes
Webhook.site is a public third‑party testing tool.
Best practices:
Do not send sensitive or production data
Use test contacts and dummy payloads
Clear test URLs after debugging
Kyrios does not provide direct support for third‑party webhook tools, but payload inspection is recommended for advanced troubleshooting.