Konverda Support

Connecting through Zapier or Make

How to push every order to the generic connection without writing code, with the field mapping and the consent-as-text trap.

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

If your platform has an app on Zapier or on Make (formerly Integromat) — PrestaShop, Squarespace, Shopify, Stripe, Ecwid and hundreds more — you can push every order to the Orders API without touching code. The contract is the same; only who makes the request changes.

Your URL is in the app, under «Ajustes → Integraciones → Conexión genérica» (settings → integrations → generic connection).

Zapier

  1. Create a Zap with your platform’s trigger: New Order (or equivalent).
  2. Add the Webhooks by Zapier action → POST event.
  3. In URL, paste the address of your generic connection.
  4. In Payload Type, choose json.
  5. Map the order’s fields following the table below. The names go in Data; for the customer object use the double-underscore notation: customer__phone, customer__name.
  6. If your checkout has a consent checkbox, map consent — and make sure it arrives as a real boolean.
  7. Test the Zap: the response should be {"ok":true,…}. The sale will appear under «Ajustes → Integraciones → Catálogo» (settings → integrations → catalogue) and, if the phone number is recognisable, on the contact.

Make

Make’s HTTP module plays the same role as Webhooks by Zapier.

  1. Create a scenario with your platform’s trigger (Watch Orders or equivalent).
  2. Add the HTTP module → Make a request.
  3. URL: the address of your generic connection. Method: POST.
  4. Body type: Raw · Content type: JSON (application/json).
  5. In Request content, build the JSON with the order’s fields following the table below.
  6. If you send consent, write it without quotes in the JSON (true / false). With quotes the request is rejected with bad_consent.
  7. Run it once: the response should be {"ok":true,…}.

Example Request content in Make, with the trigger’s variables in braces:

{
  "order_ref": "{{1.order_number}}",
  "total": {{1.total}},
  "currency": "{{1.currency}}",
  "customer": {
    "phone": "{{1.billing.phone}}",
    "name": "{{1.billing.name}}"
  },
  "consent": {{1.marketing_opt_in}}
}

Field mapping

Field to sendWhere to find it in your trigger
order_refYour platform’s order ID or order number. It has to be stable: it is the deduplication key.
totalThe total amount of the order.
currencyThe order’s currency, 3 letters.
customer.phoneThe billing or shipping phone number.
customer.nameThe customer’s name.
itemsThe order’s line items (id/SKU, name, quantity, line total).
consentThe checkout’s consent checkbox, if there is one. Send it as a real boolean, not as text.

The full contract — every field, the responses and the error catalogue — is in Orders API.

What you sendResulting opt-inWhat they can receive
consent: true«Marketing»Campaigns, waves, proactive automations and 1
templates. Lifts a previous opt-out.
consent absent«No»Only replies when the person writes. The order.paid automation is NOT sent.
consent: falseUnchangedThe sale is only recorded if the phone number was already a registered contact.

Full detail 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.Stores and payment gatewaysConcrete recipes for PrestaShop, Wix, Squarespace, Shopify and Stripe — all of them into the generic connection, each with its own traps.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