Webhooks integration for custom store and CRM workflows
Dedicated, secure endpoints to ingest JSON payloads from any custom backend, form, or ERP: complete request logging, status codes, and instant replay capability.
In short
Using webhooks in StoreChart allows any custom application, headless frontend, or external system to transmit orders, customer records, and leads as authenticated JSON payloads. Each incoming request is validated, parsed, and logged in real-time integration monitors with response times and HTTP status codes, making debugging and retries straightforward.
Webhooks for receiving orders and leads
A unique URL per store or lead channel creates records from JSON.
- Orders sent as JSON to a store's webhook URL are created in StoreChart with their line items, customer and shipping details.
- The unique token in the URL authenticates every request, and deactivating the integration stops the URL from accepting data.
- Duplicate orders are detected by the external order ID, so a retried request doesn't create a second order.
- A lead webhook turns form and landing-page submissions into leads in StoreChart.
How to set up an inbound webhook
From creating a webhook URL to your first order.
Add a custom webhook integration to a store (or set up a lead channel for leads) and copy its unique URL.
Have your system send an HTTP POST with the order or lead as JSON, for an order: its external ID, status, total, customer details, line items and shipping information.
A valid request creates the order immediately. An invalid one gets a response that lists exactly which fields to fix.
Every request that reaches a store's order webhook, accepted, rejected or duplicate, is recorded in the integration logs with its payload, so a sending system that starts failing is visible right away.
What inbound webhooks give you
Orders and leads
An order webhook per store and a lead webhook per lead channel, each with its own URL.
Full payload
One request carries the whole order, customer, line items and shipping, with no follow-up API calls.
Token authentication
Each URL contains a unique token tied to one store or lead channel; requests with an unknown or inactive token are rejected.
Duplicate protection
Orders are deduplicated by their external ID and leads by the content of the submission, so retries are safe.
Customer matching
Customers are matched by phone first and email second, so an order from a returning buyer attaches to their existing customer record.
Clear validation errors
A payload that doesn't match the schema is rejected with a list of the invalid fields, and the attempt is logged for troubleshooting.
Inbound webhooks in StoreChart
Each custom integration has its own webhook URL, and the integration logs list every request it received with its status.

Webhooks for receiving data: a developer guide
Sending a request to the webhook URL
Inbound webhooks push orders and leads into StoreChart the moment they happen, instead of someone re-entering them by hand.
- Request: an HTTP POST with a JSON body.
- URL: the unique URL of a store's custom webhook integration, or of a lead channel.
- Token: the token in the URL is the credential. Keep it server-side like a password, never in browser code.
- One way: webhooks are inbound only. StoreChart doesn't send its own events out.
Validation and errors
Every order payload is checked against a schema before anything is written.
- 422 response: a request with missing or malformed fields is rejected, with a list of the invalid fields.
- Integration logs: the attempt is recorded with the raw payload, so you see exactly what the sending system sent.
Retries and duplicates
Networks fail, so the sender should retry when it gets no clear success response. That's safe:
- Orders: recognized by their external order ID and not created again.
- Leads: deduplicated by their content.
- 429 response: requests are rate-limited per token. A sender that gets a 429 should back off and retry later.
Customer and product matching
On the receiving side, StoreChart does the matching work.
- Customers: identified by phone first, then email, so a returning buyer's order joins their existing record.
- Products: line items are matched to your products by SKU.
- Any source: a custom-built store, an ERP or a Make.com scenario gets the same handling as the WooCommerce and Shopify connections.
Order management in StoreChart
Frequently asked questions
What format should the request use?
An HTTP POST with a JSON body. For orders, the body includes the external order ID, status, total, currency, customer details, line items and shipping information, and it is validated against the schema on every request.
What happens if the same order is sent twice?
StoreChart checks the external order ID, recognizes that the order already exists, and doesn't create it again. That makes it safe for the sending system to retry a request it isn't sure went through.
What can I send to StoreChart?
Orders, through a store's custom webhook, and leads, through a lead channel's webhook. StoreChart doesn't send its own events out to other systems.
How is a request authenticated?
By the unique token in the webhook URL. The token identifies the store or lead channel the data belongs to, so keep the URL private and server-side, and deactivate the integration if it is ever exposed.
What happens when a payload is invalid?
The request is rejected with a 422 response that lists each invalid field, and the attempt is recorded in the integration logs with the raw payload, so you can see exactly what the sending system sent.
Is there a rate limit?
Yes. Requests are rate-limited per webhook token to protect the system. A sender that exceeds the limit receives a 429 response and should retry later.
Can I use inbound webhooks with Make.com or Zapier?
Yes. Any tool that can send an HTTP POST with JSON, including Make's HTTP module and Zapier's webhook action, can send orders or leads to StoreChart's webhook URLs.
Create your first inbound webhook
Copy a URL, send a JSON order and check the integration logs.
