Incoming webhook trigger

The Incoming webhook trigger lets an external system start an Omnifox workflow with an HTTP request. Connect stores, ERPs, forms and payments.

Jun 26, 2026

Watch this step in the video · Scheduled and incoming webhook

The Incoming webhook trigger lets an external system start an Omnifox workflow by sending an HTTP request. It's the entry point for connecting your store, your ERP, forms, payment gateways, or any app that can call a URL: when something happens on their side (an order paid, a new lead, a shipment dispatched), your workflow reacts instantly.

Requirements

  • A plan that includes API access to Omnifox.
  • An external tool able to make an HTTP request (Zapier, Make, your backend, etc.).

Steps

  1. Open Workflows → Create workflow.
  2. Click Add trigger and pick Incoming webhook.
  3. Save the workflow: Omnifox automatically generates a unique incoming webhook URL with a secret token, like https://omnifox.io/workflows/webhook/{token}.
  4. Copy that URL and paste it into the external system as the webhook destination (it can be GET or POST; usually POST with a JSON body).
  5. (Optional) In the JSON path match filter, limit the flow to certain events, for example event.type == "order.paid", so it only fires when the payload meets the condition.
  6. In your nodes, use the received data with the {{$webhook.payload}} (full JSON body), {{$webhook.headers}} and {{$webhook.timestamp}} variables. You can drill into the JSON, e.g. {{$webhook.payload.customer.email}}.
  7. Activate the workflow.

Verify it

Have the external system send a test event (or use the editor's Test button by pasting a sample JSON). A successful call responds {"ok":true} with HTTP 200. Then open the Executions tab to confirm the workflow ran and inspect what arrived in $webhook.payload.

If it doesn't work

  • HTTP 404 (not_found): the URL/token is wrong, or the workflow isn't Active with the Incoming webhook trigger. Re-copy the URL from the editor.
  • The flow doesn't advance: check the JSON path filter; if the condition isn't met, the workflow won't continue.
  • Data missing in the nodes: make sure the external system sends Content-Type: application/json and that your variable path matches the actual JSON structure.

Tip: treat the webhook URL as a secret. Anyone who has it can fire your workflow. If it leaks, save the workflow again to rotate the token.

Tip: can't control the external system's format? Use Zapier or Make as a middleman to shape the JSON before sending it to Omnifox.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp