Webhooks and Notifications
Limio provides several mechanisms to notify external systems about order events. These range from asynchronous webhooks, to Salesforce Platform Events for CRM automation, to error webhooks for monitoring.
Asynchronous Webhooks
Async webhooks are separate from the plugin pipeline. They are non-blocking — they cannot affect the order outcome — and are used for notifications, data synchronisation, and analytics.
The available webhook types, their payload schemas and the configuration steps are documented once, in the developer docs:
Webhooks Overview — every webhook type and its payload
Using Webhooks — how to configure and authenticate them
Salesforce Platform Events
If you use the Salesforce V3 plugin, Limio can publish Platform Events (i42as__OrderEvent__e) to your Salesforce org. These events allow you to build automation using Salesforce Lightning Flows — no code required for basic data mapping.
Supported Event Types
These are the values Limio publishes in the event's Type field (i42as__Type__c). Several Limio order types share a single event type, so branch on i42as__OrderType__c when you need to tell them apart.
NEW_ORDER
New subscription purchase, including gift purchases
new, submitted
CHANGE_OFFER
Offer switch/upgrade/downgrade
change_offer
CANCEL_REQUEST
Subscription cancellation, or an intent to cancel
cancel_subscription, cancel_intent
ADD_OFFER
Additional offer added
add_offer, credit
CHANGE_PAYMENT_REQUEST
Payment method change
change_payment
COMPENSATION_PAYMENT
Refund processed
refund
REQUEST_RENEWAL
Subscription renewal
renew
CHANGED_DELIVERY_ADDRESS
Delivery address update
change_address
UPDATE_SUBSCRIPTION
Subscription modification, or a customer details update
update_subscription, update_customer_details
DATA_CAPTURE
Data capture form submission
data_capture
How Platform Events Work
The Salesforce V3 plugin fires a Platform Event to your Salesforce org as part of order processing.
A Platform Event-Triggered Flow in Salesforce listens for the event.
The Flow maps event fields to Salesforce objects (e.g., Account, Opportunity, Asset).
Salesforce records are created or updated based on the mapping.
If you use the Limio for Salesforce managed package, a pre-built Flow (Listen to Limio OrderEvent__e) is included. Otherwise, you can create a Flow from scratch.
Configuring Which Events Are Sent
You can choose to send events for all order types or only specific ones (e.g., just new orders and cancellations). The orderTypes option on the Salesforce V3 plugin controls this.
Sending the Full Order Payload
By enabling the sendWholeOrder option, the i42as__LimioOrder__c field is populated with a JSON string containing the Limio order object. This provides access to customer details, custom fields, billing data, and tracking information within your Salesforce Flows.
Most event types send a reduced version of the order rather than the whole thing. See Platform Events Field Definitions for which types send the reduced order and which send it in full.
Additional fields can be included using the orderDataOptions configuration. Contact support@limio.com to configure this.
Learn More
Error Webhook
The Error webhook fires when any plugin fails during order processing. It provides visibility into failures across the entire orchestration pipeline and can be used for alerting, logging, or triggering recovery workflows.
When Does It Fire?
Any time a plugin in the orchestration pipeline fails — whether it's a billing failure in Zuora, a Salesforce error, a callout timeout, or any other plugin error.
The most common use case is catching payment failures.
How to Configure
Go to Settings > General Settings > Webhooks
Under Error Reporting, enter the destination URL
Payload
Each POST request includes:
eventId
The Limio event ID for tracing
processEventId
The process event ID for detailed investigation
event
The original order payload
pluginErrorOutput
Array of plugin errors with name and message
Example:
Custom Post-Processing Webhooks
For advanced requirements, Limio supports custom webhook plugins that run in the post-processing phase — after all standard plugins have completed. These webhooks have access to enriched order data, including CRM IDs and gift codes created during processing.
Custom post-processing webhooks are useful for fulfilment notifications that require data generated during order processing (e.g., a Salesforce Account ID or Zuora subscription number).
Contact support@limio.com to discuss custom webhook requirements.
Last updated
Was this helpful?

