Konverda Support

Stores and payment gateways

Concrete recipes for PrestaShop, Wix, Squarespace, Shopify and Stripe — all of them into the generic connection, each with its own traps.

View .md Updated 2026-08-26
On this page

These platforms do not have a native connector (yet): they connect to the Orders API, directly or through Zapier / Make. It works today, and it is the same contract any other tool uses.

In the app, each card’s «Solicitar» (request) button records your interest: that is what decides which native connector gets prioritised. It does not promise a date, because there isn’t one.

PrestaShop

Two routes, both reliable.

  1. Option A — Zapier: use the PrestaShop app as the trigger (New Order) and follow the Zapier guide.
  2. Option B — webhooks module: install a webhooks module on your PrestaShop and configure a paid-order notification towards your generic connection’s URL.
  3. Map the fields to the contract: only order_ref is required, but total and customer.phone are what make the record useful.

Wix

Wix Automations can send an HTTP request on every order — straight to the generic connection, with nothing in between.

  1. In your Wix dashboard: Automations → + New Automation → Order Placed (or Payment Received) trigger.
  2. Action: Send HTTP Request → method POST → URL: your generic connection’s.
  3. Body: JSON with the Wix order variables mapped to the contract (order_ref = order number, total, customer.phone = the buyer’s phone…).
  4. Save and place a test order: it should answer {"ok":true,…}.

Squarespace

Squarespace does not offer order webhooks of its own — the reliable route is its Zapier app.

  1. In Zapier, create a Zap with the Squarespace → New Order trigger.
  2. Follow the Zapier guide: Webhooks by Zapier / POST action towards your generic connection.
  3. Map order_ref (order number), total and customer.phone as a minimum.

Shopify

Today Shopify connects through Zapier (or Make) towards the generic connection. The native integration — signed webhooks, no intermediary — is on the plan, with no committed date.

  1. In Zapier, create a Zap with the Shopify → New Paid Order trigger.
  2. Webhooks by Zapier action → POST towards your generic connection.
  3. Payload Type json. Map order_ref (Order Number), total (Total Price), customer__phone (Phone or Shipping Phone) and customer__name.
  4. The order’s line items go in items — id (SKU or Variant ID), name, quantity and total per line.
  5. Test the Zap: the response should be {"ok":true,…}.

Stripe

Stripe does not send orders in the shape the generic connection expects, so today’s route is Zapier or Make translating the payment into the contract.

  1. In Zapier, create a Zap with the Stripe → New Payment trigger (or Checkout Session Completed in Make).
  2. Webhooks by Zapier action → POST towards your generic connection.
  3. Map order_ref to the ID of the payment or of the checkout session — it is the deduplication key, so it has to be stable.
  4. total = the amount divided by 100 (Stripe works in cents) · currency = the payment’s currency · customer__phone and customer__name if the Checkout collects them.
  5. Test with a test payment: the response should be {"ok":true,…}.

None of these recipes sends consent on its own. If your checkout has a real «I agree to receive WhatsApp messages» checkbox, map it to consent as a boolean — that is what decides whether the buyer enters as a marketing contact or at level «No».

The full detail is in Orders API → Consent.

In this section

Orders API (generic connection)The HTTP endpoint that records an order — or a cart someone has started to pay for — from any tool. Exact contract, field reference, responses, the 422 error catalogue and which contact level each payload creates.Capture points APIThe public endpoint that turns a submission from another platform into contact + consent. Exact contract, fields, responses, the August 2026 change and which contact level each submission creates.Connecting through Zapier or MakeHow to push every order to the generic connection without writing code, with the field mapping and the consent-as-text trap.WooCommerceThe native connector with signed webhooks, the checkout consent field, and the snippet that carries the link token all the way to the order.

Still stuck? Contact support