Connect Klipy to Zapier with your own Zaps

What Zapier does for Klipy today

There's no published Klipy app in Zapier's directory, so there's no drag-and-drop "New Klipy contact" trigger or "Create Klipy deal" action to pick from a list. You wire the connection yourself, using Zapier's own tools.

What you get instead: Klipy exposes the same building blocks Zapier's built-in "Webhooks by Zapier" step is designed to call, a REST API and outbound webhooks. You wire the connection once, in Zapier's own builder, no custom code required.

How Klipy connects to Zapier

Two routes, both running through Zapier's own "Webhooks by Zapier" step against Klipy's open surfaces.

Trigger a Zap from a Klipy event

Add a "Webhooks by Zapier" trigger step in Zapier, choose Catch Hook, and copy the unique URL it generates. Register that URL as an endpoint in Klipy's Settings → Webhooks console (the embedded Svix portal) and subscribe it to the events you want, for example lead.captured or deal.moved. Every time that event fires in Klipy, Zapier catches the payload and the rest of the Zap runs.

Here's what a lead.captured payload looks like when it lands in your Catch Hook:

{
  "type": "lead.captured",
  "object": "event",
  "data": {
    "id": "h7w8y2f1",
    "first_name": "Jordan",
    "last_name": "Patel",
    "email": "jordan.patel@acmeanalytics.com",
    "title": "Head of Growth",
    "company_name": "Acme Analytics",
    "company_domain": "acmeanalytics.com",
    "industry": "SaaS",
    "employee_count": 350,
    "estimated_revenue": 1200000,
    "city": "Austin",
    "state": "TX",
    "country": "US",
    "linkedin": "https://linkedin.com/jordan-patel"
  }
}

Source: How do Klipy webhooks work?

Call Klipy from a Zap

Add a "Webhooks by Zapier" action step (POST, PUT, or a custom request), point it at https://api.klipy.ai/api/v2/{resource}, and send your klipy_live_* key in the X-Klipy-Api-Key header. Any trigger elsewhere in your stack, a form submission, a spreadsheet row, another tool, can now create or update a Klipy contact, company, or deal.

curl https://api.klipy.ai/api/v2/contacts \
  -X POST \
  -H "X-Klipy-Api-Key: <key>" \
  -H "Idempotency-Key: 8f14e45f-ceea-4b0a-9127-1e2e3c3c1a1a" \
  -H "Content-Type: application/json" \
  -d '{"email": "person@example.com"}'

The Idempotency-Key header matters here: if a Zap step retries after a network hiccup, Klipy won't create a duplicate contact.

Source: How does the Klipy API work?

The same recipe works with n8n and Make, since both run on the identical REST API and webhooks underneath, so the setup work isn't locked to Zapier specifically. One honest caveat: how fast any of this fires depends on Zapier's own polling or trigger cadence and your Zapier plan, not a latency guarantee from Klipy.