> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lekalao.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> n8n, Zapier, Make and WordPress: Lekalao in the tools you already run.

Every connector speaks the same [API](/developers/introduction) and receives the same signed [webhooks](/developers/webhooks). They live in the application's repository, under `integrations/`.

| Tool                        | What exists                                                                                       |
| --------------------------- | ------------------------------------------------------------------------------------------------- |
| **n8n**                     | A node and a trigger (`n8n-nodes-lekalao`) — the natural companion of a self-hosted installation. |
| **Zapier**                  | Six instant triggers, three actions.                                                              |
| **Make**                    | No app of its own yet: Make's generic modules do the work, below.                                 |
| **WordPress + WooCommerce** | A plugin: forms, customers, orders and abandoned baskets.                                         |

All of them ask for two things: the **API address** of your installation, without `/v1`, and an **API token** with the **write** ability (**Settings → API tokens**). The connection test calls [`GET /v1/me`](/api-reference/introduction).

## n8n

**Lekalao** (actions): add or update a subscriber — never a duplicate —, tag, unsubscribe; record an [event](/developers/events); send a transactional e-mail. **Lekalao Trigger**: someone subscribed, confirmed, unsubscribed, was tagged; a campaign was sent; an e-mail bounced; someone complained — for every list or for one.

Switching a workflow on registers a webhook in your team; switching it off removes it. Every call is signed, and a call whose signature does not match starts nothing.

```bash theme={null}
cd integrations/n8n && npm install && npm run build
```

Install it in n8n from **Settings → Community nodes**, or mount `dist` in `~/.n8n/custom`.

## Zapier

Triggers: new subscriber, subscription confirmed, unsubscribed, tag added, e-mail bounced, campaign sent. Actions: add or update a subscriber, record an event, send a transactional e-mail. Each user gives the address of **their** Lekalao, so one app serves the cloud and every self-hosted installation that can be reached from the internet.

```bash theme={null}
cd integrations/zapier && npm install
npx zapier login && npx zapier register "Lekalao"   # once
npm test && npm run validate && npm run push
```

## Make

1. **To start a scenario**: a *Webhooks → Custom webhook* module; paste its address into **Settings → Outgoing webhooks → Add**, with the events you want. To check the signature, add a filter comparing the `X-Lekalao-Signature` header with `sha256(body; secret)`.
2. **To act in Lekalao**: an *HTTP → Make a request* module with `Authorization: Bearer <token>` — for instance `POST /v1/lists/{list}/subscribers` with `{"email": "…"}`, or `POST /v1/events`. Add `Idempotency-Key: {{uuid}}`: a scenario that is replayed does not subscribe twice.

## WordPress and WooCommerce

Upload `integrations/wordpress/lekalao` to `wp-content/plugins/`, activate it, then **Settings → Lekalao**: the API address, the token, the list.

* **A form anywhere**: `[lekalao_form]`, or `[lekalao_form list="…" names="yes" button="Subscribe"]`. The form posts to your own site, which speaks to Lekalao: the token never reaches a visitor's browser.
* **At checkout**: a box to subscribe, whose wording is yours.
* **Orders**: a paid order is sent as the event `order`, with its amount — counted as revenue of the e-mail that earned it — and the order number as reference, so it counts once.
* **Abandoned baskets**: a basket nobody touched for an hour, whose owner is known (a signed-in customer, or the address typed at checkout), is sent as `cart.abandoned` with its items, its total and a link back.

These are the events the ready-made journeys **After a purchase** and **Abandoned basket** start from: see [Automations](/automations/overview#ready-made-journeys).

## What connectors lean on

| Call                               | For                                                                                                                 |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| `GET /v1/me`                       | Whose token this is, in which team, with which abilities: the connection test.                                      |
| `POST /v1/webhooks`                | Registers a webhook and returns its `secret` **once**. See [Webhooks](/developers/webhooks#registering-by-program). |
| `DELETE /v1/webhooks/{id}`         | Removes it, when the workflow is switched off.                                                                      |
| `GET /v1/webhooks/samples/{event}` | The exact shape of a call, made from the team's latest real subscriber when there is one.                           |