LinkedIn, wired into
your stack.
Curviate is built to sit between LinkedIn and the tools you already run: workflow platforms, lead databases, CRMs, agents. The REST API and 20+ webhook event types connect any of them today; packaged connectors ship next.
Packaged connectors below are Coming soon. Webhooks and the REST API are the supported path today.How do I connect LinkedIn to my tools right now?
Two primitives cover almost every integration on this page, and both are Available now.
Your systems hear about LinkedIn events
Register your tool's inbound-webhook URL and LinkedIn events arrive as HMAC-signed POSTs, chosen from 20+ event types; every workflow platform below ingests webhooks natively.
Any tool can drive any action
Any tool that can make an HTTP request can drive any of Curviate's 120+ LinkedIn actions with one Bearer token.
Wiring n8n takes three steps today: create a webhook trigger in n8n, register its URL with Curviate and pick your events, branch on the event field. The same shape works in Make and Zapier. The packaged connectors below remove the setup, not the capability.
Workflow platforms
n8nComing soonTrigger flows on LinkedIn events and call LinkedIn actions as native n8n nodes. Until then: inbound webhooks work today.
MakeComing soonLinkedIn scenarios without custom HTTP modules. Until then: the REST API is one HTTP module away.
ZapierComing soonZaps that react to accepted connections and new messages. Until then: Zapier's webhook trigger ingests Curviate events directly.
GTM and lead data
ClayComing soonEnrich a Clay table, then let LinkedIn outreach run from the same list, with acceptance events flowing back into the table.
ApolloComing soonMove from list-building in Apollo to paced LinkedIn outreach without a CSV in between.
InstantlyComing soonCoordinate email sequences with LinkedIn touches instead of running them blind to each other.
SmartleadComing soonSame shape: multi-channel sequencing where the LinkedIn leg is typed API calls, not a browser plugin.
These tools own the lead list; Curviate owns the LinkedIn leg. The REST API already connects the two anywhere a webhook or HTTP request fits.
CRM and ATS
HubSpotComing soonLinkedIn conversations and connection events on the contact timeline.
PipedriveComing soonDeal-stage automation that reacts to LinkedIn replies.
GreenhouseComing soonCandidate records that update when Recruiter pipelines move.
Agent runtimes
Add Curviate as a custom connector and Claude operates LinkedIn natively, today, through the MCP server.
The same MCP connector inside your editor's agent, available today.
LangChainComing soonA packaged toolkit is Coming soon; the TypeScript SDK already gives a LangChain agent typed LinkedIn tools today.
The MCP server page covers setup for Claude, ChatGPT and Cursor in three steps.
Questions, answered
How do I connect LinkedIn to n8n?
Today: create an n8n webhook trigger, register its URL with Curviate, choose from 20+ event types, and branch on the event payload; n8n can also call any of the 120+ LinkedIn actions through its HTTP node with your API key. A packaged n8n node is Coming soon and removes the manual wiring.
Does Curviate integrate with Clay or Apollo?
Packaged connectors are Coming soon. What works today: export or sync your list, drive LinkedIn outreach through the REST API or CLI against those contacts, and route acceptance and reply events back via webhooks. The GTM tools own the list; Curviate owns the LinkedIn actions.
Can I pipe LinkedIn events into my CRM?
Yes, today, via webhooks: point a small handler (serverless function or workflow tool) at your CRM's API and subscribe to the events you care about, like connection.accepted and message.received. Your handler maps the event fields onto CRM records. Native CRM connectors are Coming soon.
Why should I trust the Coming soon labels?
Because the page says plainly what ships and what does not, and the parts that work today (webhooks, REST API, the MCP beta) are documented and callable right now. When a connector ships, its card flips to Available and gets its own page.
Webhooks are the outbound half of every integration here; see also what GTM engineers automate.