Overview

Order Daemon receives inbound webhooks from external systems – payment processors, automation tools, or custom services – and fires your rules in response. When an external service sends a webhook, Order Daemon evaluates matching rules and records the outcome in the Insight Dashboard.

Pro: Outbound webhooks (your store sending data to external services when a rule fires) require an active Pro licence.

Inbound webhooks

Webhook URL format

POST https://yoursite.com/wp-json/odcm/v1/webhooks/{gateway}

Replace {gateway} with the integration key provided by your payment processor or service (e.g. stripe, paypal, generic).

Health endpoint

GET https://yoursite.com/wp-json/odcm/v1/webhooks/health

Returns HTTP 200 when the plugin is active and the webhook receiver is reachable. Use this to verify your site is accessible before configuring a live integration.

Supported gateways

Order Daemon includes built-in adapters for Stripe and PayPal. Both adapters validate the gateway’s HMAC signature before processing. Configure the signing secret in your payment processor’s webhook settings and enter the same secret in Order Daemon’s webhook configuration.

The Generic gateway accepts webhooks from any service. It operates in permissive mode (no signature check) unless you configure an HMAC secret on the connection.

Security

Configure a signing secret in your external service and enter it in Order Daemon’s webhook settings. The adapter will reject requests that do not carry a valid signature.

Keep webhook URLs private. If a URL is exposed, regenerate it and update your external service.

Note: Webhook POST endpoints return HTTP 200 even when no rules matched or a non-fatal error occurred. This prevents external services from retrying unnecessarily. Check the response body for "success": true and review the Insight Dashboard to confirm rules are firing.

Verifying webhook delivery

1. Send a test event from your external service (most provide a “Send test” button in their webhook configuration screen)
2. Go to Order Daemon → Insight Dashboard
3. Find the entry – it will show the gateway name, the event type received, and which rules ran

If no entry appears:

• Confirm your site URL is correct and publicly reachable
• Verify the gateway key in the URL matches what your service expects
• Check that the signing secret matches on both sides

Outbound webhooks Pro

Pro: Requires an active Pro licence.

Outbound webhooks let Order Daemon notify external systems when a rule fires. Configure outbound webhook connections at Order Daemon → Webhooks, then add the Trigger webhook action to any rule.

Related docs

• Scheduled Automations – using cron-job.org to trigger rules on a schedule
• Payment Gateway Compatibility – which gateways are supported and known edge cases
• Webhooks API – REST API reference for managing webhook connections programmatically