Trigger: Incoming Webhook

The Incoming Webhook trigger fires a workflow when any external system sends an HTTP request to the unique URL Omnifox generates for that workflow. It's the entry point for integrating third-party tools without relying on a messaging channel.

When to use it

Use it to connect Omnifox with your ecommerce platform ("order paid" triggers a WhatsApp confirmation), a web form, Zapier/Make, or any system that can send a JSON POST.

Configuration

When you add the "Incoming Webhook" trigger to an active workflow, Omnifox generates a URL shaped like /workflows/webhook/{token} (accepts both GET and POST). You configure:

• JSON path match: filter which requests fire the workflow, e.g. event.type == "order.paid" (empty = any request fires it).

Available variables

• $webhook.payload (full JSON body)
• $webhook.headers (received HTTP headers)
• $webhook.timestamp

Example

Workflow "Order confirmation": Trigger = Incoming Webhook, filter event.type == "order.paid". Action: create/update the contact using the payload's email and send them a WhatsApp confirmation template with {{$webhook.payload.order.total}}.

Tips

• Test the webhook first with the editor's built-in test tool by pasting a real sample JSON before wiring up the external system.
• Keep the generated URL somewhere safe — anyone who has it can fire the workflow, since it's only protected by the token.

Troubleshooting

If the external system gets an error or the workflow doesn't fire, check it's sending Content-Type: application/json and that the workflow is active (not in draft); an invalid token or a paused workflow makes the request a no-op.