What n8n does, and the gap Klipy leaves
n8n is a node-based workflow tool you self-host or run on n8n Cloud: triggers, HTTP calls, data transforms, and connections across hundreds of other apps on one canvas. Klipy has no published node in n8n's directory, so there is no drag-and-drop Klipy credential type or trigger to pick from a list. What integrations does Klipy support? confirms the same pattern holds for tools like n8n, not only the named CRMs you might expect a connector for. If you came here searching for an n8n CRM integration built by Klipy, that's the honest answer: nothing bundled exists yet.
The gap is real, and it's solvable. You build the connection with two of n8n's own generic nodes, the HTTP Request node and the Webhook node, pointed at Klipy's open API and webhook surfaces.
How n8n connects to Klipy
Two of n8n's generic nodes carry the whole connection.
The HTTP Request node calls Klipy's REST API v2 (base https://api.klipy.ai/api/v2) from any step in a workflow to read or write contacts, companies, deals, pipelines, tasks, notes, and segments. Authenticate with a Header Auth credential set to X-Klipy-Api-Key (or a Bearer credential using Authorization: Bearer), holding a klipy_live_* key created in Settings → API. Batch-create up to 100 records per call for bulk moves, and set an Idempotency-Key header so a retried request with the same key returns the cached response instead of creating a second record.
The Webhook node works the other direction. Use it as the workflow's trigger, then create a matching endpoint in Klipy's Settings → Webhooks pointed at the workflow's webhook URL. Subscribe to the events you need, for example lead.captured or deal.moved, and Klipy fires the workflow the moment something changes.
No credential-mapped field discovery exists on either side, since neither tool has built the other's app. You define the field mapping between Klipy's response shape and whatever downstream tool the workflow feeds, inside the workflow itself.
Klipy's MCP server (OAuth, 38 tools, 9 scopes) sits alongside the API and webhooks, but it's built for AI agent clients like Claude and ChatGPT. We didn't confirm whether n8n's own AI-agent-facing nodes can target it, so this page claims only the API and webhook self-build route for n8n, not an MCP route.