Overview
Webhooks enable real-time syncing by reacting to events as they happen in your connected platforms. Instead of waiting for a scheduled sync, a webhook triggers a task immediately — for example, syncing a new order the moment it is created in your e-commerce platform.
You can find this page under Configure > Webhooks in the left sidebar.
How webhooks work
An event occurs in one of your connected platforms (e.g., a new order is placed or a checkout is completed).
The platform sends a notification to Junipeer's webhook endpoint.
Junipeer receives the event and creates a task to process the data.
The task runs the corresponding flow (e.g., exporting the new order to your ERP).
This happens in near real-time — typically within seconds of the original event.
Webhook subscriptions
The Webhooks page is organized by connector, with one section per platform in your integration. Each section shows:
The platform name
A Subscribe to Event area with an event dropdown
A list of active subscriptions
Adding a subscription
Find the section for the platform you want to listen to
Select an event from the Event dropdown (e.g., "CheckoutOrder.Created")
The subscription is created and Junipeer begins listening for that event
Available events
The events available depend on the platform. Not all platforms support webhooks:
E-commerce platforms typically offer events for order creation, product updates, and inventory changes.
Payment providers may offer payout or settlement events.
ERP/Accounting systems may have limited or no webhook support. If a platform shows "There are no events," it means that platform does not currently support outbound webhooks through Junipeer.
Active subscriptions
Each active subscription shows:
The event type (e.g., "CheckoutOrder.Created")
The associated task/flow that will be triggered
A verification status indicating whether the subscription is confirmed and active
A delete option to remove the subscription
Setting up webhooks
Most webhook subscriptions can be managed directly from the Junipeer Webhooks page using the event dropdown. Some platforms, however, require additional configuration in the platform's own admin panel — for example, setting up a webhook endpoint URL or enabling specific report types.
Refer to your connector-specific getting started guide for platform-specific webhook setup instructions.
Webhooks vs. scheduling
| | Webhooks | Scheduling | |---|---|---| | Speed | Near real-time (seconds) | Depends on interval (minutes to hours) | | Reliability | Depends on platform uptime | Runs regardless of external events | | Setup | May require platform-side configuration | Fully managed in Junipeer | | Best for | Time-sensitive data (orders, payments) | Regular bulk syncs (products, stock) |
For maximum reliability, use both: webhooks for immediate processing and scheduled syncs as a fallback.
Tips
If a webhook subscription shows as unverified, try removing it and re-creating it.
Not all data types benefit from webhooks. Product catalog changes, for example, are often better handled by a daily scheduled sync.
Monitor the Tasks page to confirm that webhook-triggered tasks are running successfully.
If you are not receiving webhook events, check that the source platform's webhook configuration is pointing to the correct Junipeer endpoint and that the subscription is active.