Integrations

Any tool with an HTTP step or an MCP client can use docuinked today. Native listed apps are coming soon, and each page below says exactly what works now.

What works today

Two doors are open on every platform. An HTTP step can call the REST API. An MCP client can connect to the MCP server with one URL. Neither needs anything from us beyond an API key.

What is coming soon

We don't have listed apps in any marketplace yet. Where a page says "coming soon", it means you won't find docuinked in that tool's app directory today. The HTTP or MCP route on that page is what to use now.

Which key to use

Start with a test key. For a fixed workflow you wrote yourself, a live key set to "Sends directly" is fine. For anything an AI step can steer, use "Needs my approval", so a person sees each draft. See approvals.

All integrations

• n8n e-signature integration

  You can use docuinked in n8n today in two ways: the HTTP Request node for fixed workflows, and the MCP Client Tool for AI agents. A verified community node is coming soon.

• Send contracts from a Clay table

  You can send contracts from Clay today with the HTTP API column. The trick is one header: an Idempotency-Key built from the row ID, so a rerun can never send a second contract.

• Zapier e-signature integration

  You can reach docuinked from a Zap today with Webhooks by Zapier. There is no listed docuinked app in Zapier yet. That is coming soon.

• Make e-signature integration

  A Make scenario can send documents through docuinked today with the HTTP module, and hear back through a custom webhook. A native Make app is coming soon.

• Pipedream e-signature integration

  Pipedream suits docuinked well, because its code steps can verify our webhook signature properly. Use an HTTP request or a Node.js step today. A registered app is coming soon.

• Gumloop e-signature integration

  Gumloop connects to any remote MCP server, so docuinked works there today with one URL. No listing is needed for this to work.

• Lindy e-signature integration

  A Lindy agent can use docuinked today through Lindy's MCP integration. The agent does the paperwork, and a person approves each live send.

• Relay.app e-signature integration

  Relay.app agent steps can connect to a remote MCP server, so docuinked works there today. Its human-in-the-loop style fits an approve-then-send flow well.

• Activepieces e-signature integration

  An Activepieces flow can call docuinked today with the HTTP piece, and start from a catch webhook. A docuinked piece is coming soon.