Skip to main content
ClientNest365ClientNest365

Google Drive

Mirror every client upload to Google Drive

Every file a client uploads gets a copy in a Drive folder named after the client. Useful as an offsite backup or for teams that still keep working files in Drive.

12 min setup Trigger: file.uploaded medium
works with Zapierworks with Make.com

Setup steps

  1. In Make / Zapier: create a scenario with a webhook trigger.
  2. Add a step that calls back to ClientNest365's signed-download API to fetch the file bytes (use the file_id from the webhook payload).
  3. Add a Google Drive 'Upload File' step. Target folder: dynamic, using the client.name from the payload.
  4. In ClientNest365: Settings -> Webhooks -> + New endpoint. Subscribe to file.uploaded. Target = the Make/Zapier webhook URL.
  5. Test by uploading a file from any client portal.

Payload fields you'll use

  • file.id
  • file.name
  • file.mime_type
  • client.name
  • client.slug

Where to wire it in ClientNest365

Open your workspace at /app/settings/webhooks. Click + New endpoint. Paste the target URL from your automation platform (Zapier, Make, n8n) or the third-party tool's native webhook URL. Subscribe to the file.uploaded event. Save. Your endpoint secret is shown once at creation; copy it now if you plan to verify the HMAC signature on the receiving end.

Verifying the signature

Each webhook POST carries an X-CN-Signature header. The value is sha256=<hmac> where the HMAC is computed over the raw request body using your endpoint secret. Compare with constant-time equality. Reject mismatches.