ClientLoop → Make
Point a webhook endpoint at a Make custom webhook. Verify the signing secret, then branch — Drive, Sheets, your CRM, notifications.
Make integration · formerly Integromat
Connect ClientLoop to Make (formerly Integromat)
No native app needed. The ClientLoop REST API and signed webhooks plug straight into Make's HTTP and custom webhook modules.
Example workflow
CRM trigger to document collection — one Make scenario each way
Deal moves stageYour CRM
Scenario runsMake HTTP module
Request createdPOST /api/v1/requests
Client uploadsDocuments received
Webhook firesdocument.uploaded
Scenario branchesDrive, Sheets, CRM
How it connects
Two modules. Both directions.
Make → ClientLoop
The HTTP module calls POST /api/v1/requests. A CRM deal, form or new row becomes a request — with an Idempotency-Key so retries stay safe.
The one HTTP call
What the Make HTTP module sends
POST /api/v1/requests
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: 8f14e45f-...
Content-Type: application/json
{
"email": "jane@example.com",
"name": "Jane Smith",
"template": "tmpl_onboarding_individual",
"dueInDays": 7
}- ✓ Idempotency-Key — retries never double-send
- ✓ Bearer API key auth
- ✓ Any Make trigger fills the body
Map any Make trigger's fields into the body. The Idempotency-Key makes scenario retries safe.
Receiving events → verify the signatureWorkflow examples
Scenarios teams build with ClientLoop and Make
- 01CRM deal won → onboarding request goes out
A scenario watches your CRM and calls the API with the right template. The request sends itself.
- 02Client uploads → metadata to Drive & Sheets
The document.uploaded event hits your webhook. The scenario logs the upload to a Sheet and files it in Drive.
- 03Request submitted → CRM synced, team pinged
On request.submitted, one branch writes status back to your CRM while another notifies the account owner.
- 04Look up status by your own reference
Set an external reference when you create the request, then query it later. No ClientLoop ids to store on your side.
Use cases
Built for teams that run ops in Make
CRM-triggered onboardingUpload logs in SheetsDrive folders per clientStatus sync back to CRMMulti-branch notificationsSafe retries with idempotency
FAQ
Common questions
Does ClientLoop have a native Make app?
Not yet. ClientLoop connects to Make through the generic HTTP module and the custom webhook module. Use the HTTP module to call the ClientLoop REST API, and a Make custom webhook to receive ClientLoop events. A native Make app is planned for a future release.
How do I receive ClientLoop events in a Make scenario?
Create a custom webhook in Make and copy its URL. In ClientLoop, add a webhook endpoint pointing at that URL. Every endpoint gets its own signing secret — verify the HMAC-SHA256 signature on each payload before processing it, then branch your scenario on the event type (request.submitted, document.uploaded, and other request lifecycle events).
How do I create document requests from Make?
Use the Make HTTP module to POST to /api/v1/requests with your API key as a Bearer token and a template id. Add an Idempotency-Key header so scenario retries never create duplicate requests. Any Make trigger — a CRM deal stage, a form submission, a new spreadsheet row — can kick it off.
What plan do I need?
API access and outbound webhooks are Pro plan features — £19/mo flat. That covers API keys, webhook endpoints with signing secrets, and idempotent retries.
Wire document collection into your Make scenarios
ClientLoop gives requests structure. Make connects them to everything else.
Related