Test a webhook, view delivery history and deactivate/delete
Learn how to send a test event, review the delivery history with its payloads, and deactivate or delete a webhook in Omnifox.
Watch this step in the video · Delivery history
What you'll do
Once a webhook is created, it's worth testing it, watching its delivery history, and knowing how to deactivate or delete it when you no longer need it. It all happens in the Webhooks section.
Test a webhook
There are two ways to send a test event:
- From the list: in Webhooks, on the webhook row, click the Send test event icon (▶). A quick result (success or error) appears next to the row.
- From the editor: open Edit and scroll to the Test delivery card. Click Send test: Omnifox sends a
test.pingpayload to your URL and shows the HTTP status, response time, and returned body.
The test does not affect metrics or the circuit breaker, so you can use it freely to validate your endpoint.
View the delivery history
- In Webhooks, click the webhook name to open its detail page.
- At the top you'll see cards for 24h success rate, 7d success rate, Average time, and Consecutive failures, plus the Circuit Breaker state.
- Below, under Delivery history, there's a table with Date, Event, Status (Delivered / Pending / Failed / Abandoned), Attempts, HTTP code, and Next retry.
- Use the Event, Status, and date-range filters (From / To) to narrow down; Clear resets them.
- Click View payload on any row to open the modal with the sent payload and your server's last response.
Deactivate a webhook
To pause deliveries without losing the configuration:
- In the Webhooks list, switch off the Active toggle on the row. The webhook stops sending events immediately and you can re-enable it anytime.
Delete a webhook
When you no longer need it:
- In the Webhooks list, click the Delete icon (trash) on the row, or open Edit and click Delete webhook.
- Confirm in the dialog. This action cannot be undone: the webhook and its configuration are removed.
If it doesn't work
- The test fails with a connection error: check that the URL is correct and reachable over HTTPS from the internet.
- HTTP 4xx on the test: your server rejected the payload; review authentication and headers.
- No deliveries in the history: confirm the webhook is Active and that the event happened after you created it.
Tip: before deleting a failing webhook, try deactivating it and reviewing the Delivery history to diagnose; often the issue is a changed URL or an expired token.
Related articles
Related articles
-
How to connect integrations and external apps
Connect Omnifox with your favorite tools from the integrations catalog in just a few steps.
-
Integrations and API complete guide
Integrations and API in depth, in 30 chapters: API keys, real calls, signed webhooks, n8n, MCP and SDKs, all really working.
-
Connecting Omnifox to Azur, Siigo, Alegra, QuickBooks or another accounting system or ERP
Omnifox doesn't have a native connector for accounting systems or ERPs today. Here's how to connect them anyway with workflows, the HTTP node, n8n, Make, Zapier or the API, with examples.
-
Generate and use API keys and webhooks
Create API keys to access Omnifox programmatically and set up webhooks to receive real-time events.
-
Getting started with integrations (webhook / OAuth / API key)
Connect Omnifox with your other tools: what's available today, what's coming soon, and when to use a webhook, an OAuth connection or an API key.