Example: n8n workflow
This example shows two n8n workflows: a simple digital product sale with Slack notifications, and a physical product workflow with address collection and shipping updates.
Workflow 1: Digital product with notifications
Workflow overview
Node 1: Create listing
Use an HTTP Request node to call POST /v1/listings.
Configuration:
Body:
Response fields used downstream:
{{ $json.url }}— product page URL{{ $json.slug }}— listing slug{{ $json.fulfillment }}—"managed"or"external"{{ $json.readiness.sellable }}— whether buyers can purchase
Node 2: Order webhook
Add a Webhook node to receive order events from ListBee.
Configuration:
Copy the webhook URL from n8n (e.g. https://your-n8n.example.com/webhook/listbee-orders) and register it in ListBee:
Incoming order.paid payload:
Node 3: Slack notification
Add a Slack node after the webhook node.
Configuration:
Workflow 2: Physical product with shipping
This workflow handles physical products — collecting a shipping address, processing the order, and updating shipping status.
Workflow overview
Create the listing
Process the order.paid webhook
The order.paid event includes checkout_data and shipping_address:
Use a Code node to extract the shipping details:
Ship the order
After you ship the product, use an HTTP Request node:
Body:
Mark as fulfilled
When delivered, use another HTTP Request node:
Body: {}
Using the ListBee n8n community node
If you prefer a purpose-built node over HTTP Request, install the ListBee community node:
The community node provides credential management, typed fields, and auto-completion for all ListBee endpoints. See the n8n node docs for setup instructions.
Next steps
- Fulfillment modes — managed vs external.
- Example: storefront script — bulk-create listings from a JSON catalog.
- n8n node — full reference for the ListBee community node.