Route Janis Commerce Webhooks by Event in n8n (Single URL)

Route Janis Commerce Webhooks by Event in n8n (Single URL)

Stop juggling multiple webhook endpoints. This n8n workflow receives Janis Commerce webhooks on one URL, fetches the full resource for each event, and routes the payload by event name so you can attach separate automations for orders and catalog-related events.

What this workflow does

This workflow is designed to be your central Janis Commerce webhook entrypoint:

• Receives any supported Janis Commerce event sent to a single webhook URL.
• Fetches the full resource from the originating Janis service (e.g., an order or product). The output includes an _event metadata block.
• Routes by event name using _event.eventName to matching handler branches.
• Provides basic placeholder handling for sample events (including canceled, readyForPicking, and productSaved) where you can implement your custom logic.
• Sends unmatched events to a catch-all branch you can ignore or extend with additional rules.

Use cases

• Order automation: Trigger different n8n steps when an order is readyForPicking versus when it is canceled.
• Catalog synchronization: Run separate workflows for productSaved events to update your internal product database or downstream services.
• Single webhook strategy: Keep Janis webhook configuration simple by pointing all events to one n8n endpoint.

Technical details

• Janis trigger node: uses the community node @janiscommerce/n8n-nodes-janis-commerce with a Janis API credential.
• Routing logic: implemented with switch and set (plus no op placeholders) to branch based on _event.eventName.
• Workflow structure: includes sticky note elements for readability.

Setup

• Install @janiscommerce/n8n-nodes-janis-commerce in n8n (Settings → Community Nodes).
• Create/select a Janis Commerce API credential in the Janis trigger node.
• Activate the workflow, copy the generated webhook URL, and configure Janis (OMS/Catalog/Pricing/WMS hooks) to send events to it.
• Update routing rules and replace placeholder handler steps with your business actions (HTTP requests, database writes, notifications, etc.).