DOCS

v1.3.28
 // Pro v1.2.20

 · Latest

Docs/Integrations

Integrations

Order Daemon connects to external services in two directions: inbound (an external service triggers a rule) and outbound (a rule fires a notification or API call to an external service). The webhook engine and all service adapters are Pro features that extend the core rule model with HTTP-based events.

Pro: Webhooks, the Generic adapter, and all built-in service integrations require an active Pro licence. Pro extends the core trigger and action model so your rules can interact with any external system.

Payment gateways

Order Daemon normalizes payment events from different gateways into a Universal Event model. This means you write one rule for “payment confirmed” and it fires correctly whether the payment came from Stripe, PayPal, or any other supported gateway. You do not write separate rules for each gateway or handle gateway-specific event names.

The normalization layer sits between the raw gateway webhook and the Order Daemon trigger system. When Stripe sends a payment_intent.succeeded event and PayPal sends a sale notification, both arrive as the same Universal Event in your rule. Gateway compatibility details, including known edge cases, are covered in Payment Gateway Compatibility.

External services

The webhook engine lets Order Daemon send an HTTP POST to any URL when a rule fires, and receive an HTTP POST from any external service to trigger a rule. Any service that can make an HTTP request can integrate with Order Daemon on either side.

Built-in adapters handle authentication and payload formatting for services that need more than a raw POST:

  • Stripe – inbound payment events via signed webhooks
  • PayPal – inbound payment and capture events
  • Generic webhook endpoint – any service that can send an HTTP POST
  • MailerLite – subscriber management triggered by order events
  • cron-job.org – scheduled automations via external cron, for sites without reliable WP-Cron

Child docs in this section