Overview
This node acts as a webhook trigger for various fulfillment-related events from the Fulfillmenttools platform. It listens for specific event notifications sent by Fulfillmenttools and triggers workflows in n8n when those events occur.
Common scenarios where this node is beneficial include automating responses to order lifecycle changes (e.g., order creation, cancellation), inventory updates, delivery status changes, routing plan updates, facility modifications, pick/pack job progress, handover job statuses, parcel carrier events, and return processing. For example, you could use it to automatically update your internal systems or notify teams when an order is created or when inventory stock changes at a facility.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Fulfillmenttools event to listen for. Options include: Order Created, Order Canceled, Order Unlocked, Inventory Facility Stock Changed, Inbound Delivery Received, Inbound Delivery Finished, Inbound Delivery On Hold, Routing Plan Splitted, Routing Plan Waiting, Routing Plan Fallback, Routing Plan Routed, Routing Plan Rerouteplan Created, Routing Plan Not Routable, Facility Created, Facility Updated, Facility Deleted, Pick Job Created, Pick Job Picking Commenced, Pick Job Picking Paused, Pick Job Picking Finished, Pick Job Pick Line Picked, Pick Job Rerouted, Pick Job Reset, Pick Job Aborted, Pack Job Created, Pack Job Updated, Handoverjob Created, Handoverjob Handed Over, Handoverjob Reverted, Handoverjob Canceled, Parcel Carrier Requested, Parcel Carrier Failed, Parcel Carrier Acknowledged, Return Created, Return Claimed, Return Closed, Return Canceled, Return Updated. Default is "Order Created". |
Output
- The node outputs JSON data representing the payload of the received webhook event.
- The output JSON structure corresponds directly to the body of the HTTP POST request sent by Fulfillmenttools for the selected event.
- No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Fulfillmenttools to manage webhook subscriptions securely.
- The node registers and deletes webhook subscriptions on the Fulfillmenttools platform using the provided credentials.
- The workflow must be accessible via a public URL for Fulfillmenttools to send webhook requests.
- The node expects specific HTTP headers (
x-fulfillmenttools-eventandx-fulfillmenttools-token) for validating incoming webhook requests.
Troubleshooting
- Webhook Registration Failure: If the node cannot create or verify the webhook subscription, ensure that the API credentials are correct and have sufficient permissions.
- Event Mismatch: Incoming webhook events with a different event type than configured will be ignored; verify that the selected event matches the expected webhook payload.
- Invalid Token: If the webhook token header does not match the stored credential token, the webhook data will be discarded. Ensure the token in credentials matches what Fulfillmenttools sends.
- Public URL Accessibility: The webhook URL must be publicly reachable by Fulfillmenttools. If behind firewalls or local environments, consider using tunneling services.
- Subscription Deletion Issues: On workflow deactivation, if the subscription cannot be deleted, manual cleanup might be necessary on the Fulfillmenttools side.