Connect Clinch to the tools you already use

Integration guides

One page per tool: what works today, three recipes and the exact setup.

• ZapierSend contracts for signature from any Zap, and start Zaps when a client signs, pays or books.Official app not listed yetWorks today: webhooks and HTTP requests
• MakeCreate and send contracts from Make scenarios, and trigger scenarios on signatures, payments and new leads.Official app not listed yetWorks today: webhooks and HTTP requests
• n8nSend contracts for signature from any n8n workflow and start workflows on signatures, payments, proposals, leads and bookings.Official app not listed yetWorks today: webhooks and HTTP requests
• ActivepiecesSend contracts for signature from Activepieces flows and trigger flows when clients sign, pay or book.Official app not listed yetWorks today: webhooks and HTTP requests
• WordPressEmbed your Clinch inquiry form, booking page or free calculators on any WordPress page.Official app not listed yetWorks today: embed code
• Claude & Cursor (MCP)Your AI assistant drafts the contract; Clinch gets it signed from your client's phone and requests the deposit.Official app not listed yetWorks today: paste or upload into Clinch
• Browser extensionSelect a job post or client email, right-click, and get an AI-drafted contract prefilled in Clinch.Official app not listed yetWorks today: paste or upload into Clinch
• Google DocsSend a contract written in Google Docs for mobile e-signature, with the deposit requested at signing.No dedicated appWorks today: paste or upload into Clinch
• SlackPost to a Slack channel when a contract is signed, an invoice paid, a proposal accepted or a call booked.Official app not listed yetWorks today: webhooks and HTTP requests
• REST API & webhooksCreate contracts, send them for signature, issue invoices and receive signed webhooks from your own code.Built into ClinchWorks today: Clinch API and webhooks

Events you can send

• contract.signed — every signer has signed the contract
• invoice.paid — an invoice is paid (online or marked paid by hand)
• proposal.accepted — a client picks a package on your proposal
• inquiry.created — a lead fills in your inquiry form
• booking.created — someone books a call on your booking page

What freelancers automate

• Contract signed → project created

  Open a Trello card, Asana project or Notion page the moment the deal is signed in Clinch.

• Invoice paid → books updated

  Record the payment in QuickBooks, Xero or FreeAgent without typing it twice.

• New lead → CRM

  Every inquiry from your Clinch form lands in HubSpot, Pipedrive or Airtable with name, budget and project type.

• Anything → Slack or Discord

  Post "Acme just signed" or "Invoice #12 paid" to your team channel.

• Everything → Google Sheets

  Keep a running revenue and pipeline sheet fed by real events, not memory.

• Call booked → calendar and prep

  Add the call to Google Calendar, create a Zoom link and send a prep email.

Zapier

1. In Zapier, create a Zap with the trigger "Webhooks by Zapier → Catch Hook" and copy the URL it gives you.
2. In Clinch, open Settings → Integrations, paste the URL, pick the events and click Add webhook.
3. Click "Send test" in Clinch, then "Test trigger" in Zapier: the sample event and its fields appear.
4. Add the action you want (Trello, QuickBooks, Slack, Sheets…) and map the fields. Turn the Zap on.

Make (Integromat)

1. In Make, add a "Webhooks → Custom webhook" module and copy its address.
2. Paste it in Clinch under Settings → Integrations and click Add webhook.
3. Click "Send test" in Clinch so Make can learn the data structure.
4. Connect the next modules and switch the scenario on.

n8n (self-hosted or cloud)

1. Add a Webhook node set to POST and copy the production URL.
2. Paste it in Clinch under Settings → Integrations.
3. Optionally add a Code node that checks X-Clinch-Signature with your signing secret.
4. Continue the workflow with any of n8n's 400+ nodes and activate it.

Signed, retried, logged

Each request is signed with HMAC-SHA256 using a secret only you see, retried up to three times if your endpoint is down, and listed in your delivery log. Clinch only sends to public https addresses.