# 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.

Fuente / source: https://soporte.konverda.com/en/docs/developers/zapier-and-make
Idioma / language: en
Actualizado / updated: 2026-08-26

---
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](/en/docs/developers/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 {#zapier}

:::pasos
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](#field-mapping). 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.
:::

:::aviso
Zapier usually sends text. A quoted `"true"` is rejected with `422 bad_consent`: consent is not guessed. Use a formula that produces a real `true` / `false`, not `"Yes"` / `"No"`.
:::

## Make {#make}

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

:::pasos
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](#field-mapping).
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:

```json
{
  "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-mapping}

| Field to send | Where to find it in your trigger |
|---|---|
| `order_ref` | Your platform's order ID or order number. It has to be **stable**: it is the deduplication key. |
| `total` | The total amount of the order. |
| `currency` | The order's currency, 3 letters. |
| `customer.phone` | The billing or shipping phone number. |
| `customer.name` | The customer's name. |
| `items` | The order's line items (id/SKU, name, quantity, line total). |
| `consent` | The 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](/en/docs/developers/orders-api#fields).

## Which contact level each payload creates {#consent}

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

Full detail in [Orders API → Consent](/en/docs/developers/orders-api#consent).

## Read next {#read-next}

- [Orders API (generic connection)](/en/docs/developers/orders-api)
- [Stores and payment gateways](/en/docs/developers/stores-and-gateways) — concrete per-platform recipes.
- [The marketing opt-in and «Añadir a marketing»](/en/docs/contacts-and-consent/the-marketing-opt-in)