Is it a webhook problem or an automation problem?

First, determine whether the event arrived at DMHub at all.

Check the webhook delivery log: Go to /settings/integrations → your webhook → Delivery Log.

If the event appears here, DMHub received it — the issue is in your automation logic.

If the event is missing, the problem is before DMHub — in the sending system's webhook delivery or the DMHub webhook URL configuration.

Diagnosing delivery failures

1. Webhook URL is wrong

Go to the external system's webhook settings and verify the URL matches exactly:

https://www.dmhub.ai/api/webhooks/inbound/wh_abc123xyz

Common mistakes: extra slash, wrong endpoint, HTTP instead of HTTPS.

2. SSL certificate error

DMHub uses TLS. If the sending system is checking SSL certificates, ensure there's no certificate issue on your end. Test with:

curl -X POST https://www.dmhub.ai/api/webhooks/inbound/wh_abc123xyz   -H "Content-Type: application/json"   -d '{"test": true}'

A 200 response means the URL is reachable.

3. Payload format mismatch

DMHub expects JSON. If the sending system sends form-encoded or XML data, the webhook will fail silently. Check the Content-Type header in the delivery log.

4. Signature validation failure

If you're using signed webhooks, verify the secret matches on both sides. Go to /settings/integrations → your webhook → Secret to view or rotate the secret.

Diagnosing automation failures

If the event arrived but the automation didn't fire:

Go to /automations → select your automation → Runs
Look for recent run attempts — a failed run shows the step that errored
Common issues:

- Trigger condition doesn't match (check filter logic) - Referenced variable doesn't exist in the payload - Automation is paused or inactive

Manual re-trigger

From the automation run log, you can Replay a failed run. This re-processes the same event through the automation logic — useful after you've fixed a bug.