Save approved files to Google Drive or Dropbox

GarnerDocs deletes files at the end of your retention period, so the copy you keep belongs in your own storage. You can send every file you approve to Google Drive, OneDrive or Dropbox on its own, with a webhook and Zapier or Make.

GarnerDocs doesn't connect to these services itself. The webhook tells Zapier or Make that you approved a file, and their storage step saves it. You set it up once, and it runs for every request.

Set it up with Zapier

1. 1

   Start a Zap with a webhook

   In Zapier, create a Zap. Choose Webhooks by Zapier as the trigger, then Catch Hook, and copy the webhook URL.

2. 2

   Add the endpoint in GarnerDocs

   Go to Settings → Webhooks and select Add endpoint. Paste the URL, tick only File approved, and tick Include download links.

3. 3

   Send a sample

   Approve a test file on a request, then go back to Zapier and find the new record. Zapier needs a real upload.approved event to show you the fields. Send test event only sends a ping, which has no file.

4. 4

   Add your storage step

   Add an action for your storage app, such as Google Drive, Microsoft OneDrive or Dropbox, and choose its upload file action. Choose the folder, and put the upload's download URL (data.upload.download_url) in the file field. Zapier fetches the file from that link.

5. 5

   Name the file

   In the file name field, combine fields from the event. See Name your files below.

6. 6

   Publish the Zap

   Test the step, check the file arrived, then publish.

Set it up with Make

1. 1

   Start a scenario with a webhook

   In Make, create a scenario that starts with Webhooks, then Custom webhook. Add a webhook and copy its address.

2. 2

   Add the endpoint in GarnerDocs

   Go to Settings → Webhooks and select Add endpoint. Paste the address, tick only File approved, and tick Include download links.

3. 3

   Send a sample

   In Make, select Run once, then approve a test file in GarnerDocs. Make learns the fields from that event.

4. 4

   Fetch the file

   Add the HTTP app's Get a file module, and map data.upload.download_url to its URL.

5. 5

   Upload it to your storage

   Add your storage app's upload module, such as Google Drive, OneDrive or Dropbox. Choose the folder, use the file from the HTTP module, and set the file name.

6. 6

   Turn the scenario on

   Save it and switch it on. Leave its schedule at Immediately, so each file is saved as soon as you approve it.

Name your files

Each event carries the client, the request, the checklist item and the file, so you can name files the way your firm already does. Useful fields:

For example, Harbour Lane Ltd - 2025 annual accounts - Bank statements - statements-jan-dec.pdf. End the name with data.upload.name so the file keeps its extension.

To keep a folder per client, add a step before the upload that finds a folder by the client's name and creates it when it doesn't exist. Zapier's Google Drive Find a Folder step can do this. Then upload into the folder it returns.

If a file doesn't arrive

• Each download link lasts 1 hour. Don't add a delay or approval step before the storage step. Make's schedule should stay at Immediately.
• To try again later, open the endpoint in Settings → Webhooks and select Resend on the delivery. Each resend comes with a fresh link. Replaying the old run in Zapier or Make after the hour has passed won't work.
• Check the endpoint's recent deliveries. If they failed, the problem is between GarnerDocs and Zapier or Make. If they were delivered, look at the Zap's or scenario's history.
• Was the file approved while the endpoint was paused or turned off? Nothing is sent then, and there's nothing to resend. Resume the endpoint, and download the files you missed.

Good to know

• Only files you approve after setting this up are saved. For earlier requests, download all files as a ZIP.
• One file is saved per approval, including when you approve several files at once. Each one is saved as a new file: GarnerDocs never overwrites or removes anything in your storage.
• Nothing is sent about a restricted request, so its files aren't saved this way. Download them instead.
• Short answers aren't sent, because their text is never in a webhook. They're in the request's ZIP.
• Copies in your storage are yours. Deleting files in GarnerDocs, or at the end of the retention period, doesn't touch them.
• Files go to Zapier or Make and to your storage, which you choose and control. Subprocessors
• For every field and the signature check, see webhooks.