> ## Documentation Index
> Fetch the complete documentation index at: https://paperplane-justin-winter-s-projects.vercel.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations (Zapier, n8n, Make)

> Connect paperplane to your workflow — what works today and the native-app roadmap.

## Today: connect with plain REST + webhooks

Because paperplane is a clean REST API with signed delivery webhooks, **every automation tool can already use it today** with its generic HTTP/webhook modules — no native app required.

### Zapier

Two Zaps cover the whole product:

* **Trigger — "New delivery webhook"**: use the **Webhooks by Zapier** trigger (Catch Hook) pointed at paperplane's outbound webhook `webhook_url` (pass one at order creation). Verify the `X-paperplane-Signature` in a Code step with your `OUTBOUND_WEBHOOK_SECRET`.
* **Action — "Create a letter"**: use **Webhooks by Zapier → POST** to `https://sendpaperplane.com/v1/orders`. (For MCP-first workflows, an agent with the MCP server is often simpler than a Zap.)

### n8n

* **Trigger**: **Webhook** node → receives paperplane's signed event; verify the signature with a Code node.
* **Action**: **HTTP Request** node → `POST /v1/orders`. n8n also supports the MCP tools if you want a native "send letter" node feel.

### Make

* **Trigger**: **Webhook** module → receives the signed event.
* **Action**: **HTTP / Make a request** → `POST /v1/orders`.

<Note>
  Outbound webhooks are only sent when `OUTBOUND_WEBHOOK_SECRET` is set — see [Delivery webhooks](/docs/guides/webhooks). Passing a `webhook_url` on order creation is what subscribes your Zap/n8n/Make to status changes.
</Note>

## Roadmap: native marketplace apps

Native apps for the marketplaces (Zapier, n8n, Make) are planned. Build vs. approval reality:

| Target                 | Buildable now?                                                              | Published when?                                                    | Effort  |
| ---------------------- | --------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------- |
| **n8n community node** | Yes — we can build + test locally, then submit to the community registry    | After a short n8n review of the published node                     | Low–med |
| **Zapier app**         | Yes — `zapier init` + actions/triggers + `zapier test` against the REST API | Requires a Zapier platform account + app review before it's listed | Med     |
| **Make module**        | Build via Make's module SDK locally                                         | Requires a Make partner/dev account + review                       | Med     |

What we've already made these trivial:

* **Signed outbound webhooks** — the trigger side.
* **A stable, generated OpenAPI spec** (`/v1/openapi.json`) — the integration tools' importers consume it directly to auto-generate actions.
* **Capability tokens** — no API keys to provision in another system; each order carries its own payment.

<Info>
  Want the native Zapier/n8n/Make app faster? Tell us which marketplace matters most — the OpenAPI spec means auto-generating a skeleton in each is mostly plumbing.
</Info>