# Connect an automation tool

> Use Zapier, Make, n8n, Pabbly or similar with HTTP and webhook steps, or build Syncon One into your own product.

- Canonical page: https://synconone.com/docs/api-automation-tools
- Section: Developers
- Updated: 2026-10-22

You can connect Syncon One to an automation tool today with the tool's own HTTP-request and webhook steps, using the same API and webhooks as any program. Zapier, Make, n8n, Pabbly Connect, Activepieces and similar tools all have them.

## Sign in

Add a header to each HTTP step: `Authorization: Bearer sk_live_YOUR_KEY`, with the base address `https://synconone.com/api/v1`. Make one key for the tool, with only the scopes its flows need.

## Start a flow when something happens

Use the tool's webhook trigger to get an address, then subscribe that address with `POST /webhooks` and the events you want (see [Webhooks](https://synconone.com/docs/webhooks)). A delivery carries only ids, so add a step that reads the record: for a new customer, `GET /people/{data.publicId}`. When the flow is switched off, delete the subscription.

If a tool cannot register webhooks, poll instead: read a list newest first, for example `GET /people?sort=-created_at&limit=50`, and skip the ids it has seen.

## Do something in Syncon One

Each action is one HTTP step: create a customer, add a note, open a ticket, schedule a meeting, reply in a chat. The [reference](https://synconone.com/docs/api-reference) gives the path, method and body for each. Send an `Idempotency-Key` on creates so a retried step does not make a second record, and show the API's `error.message` when a step fails.

## Build your own integration

If you make an automation product, you can build Syncon One into it as an app: customers paste their key as the sign-in, your triggers subscribe webhooks, and your actions call the endpoints. Generate a client from the [OpenAPI document](https://synconone.com/api/v1/openapi.json) rather than writing requests by hand.