Skip to content
Content SnareHelp centre

How cloud storage integrations work

Quick answer

A cloud storage integration automatically copies the files your clients upload into your Google Drive, Dropbox, OneDrive or SharePoint. By default, each client and each request gets its own folder. For Google Drive or OneDrive, create a new empty folder only for Content Snare and pick it when you connect.

What a cloud storage integration does

A cloud storage integration sends copies of the files your clients upload into your own Google Drive, Dropbox or OneDrive or SharePoint. Connect one, and files from your requests are copied over automatically, following the settings below.

They are copies. Your files stay in Content Snare too, so connecting a drive doesn't reduce the storage you use in Content Snare.

All three are available on every plan, the Basic plan included. FYI also stores documents, but it's an accounting integration and needs a plan that includes premium integrations. SuiteFiles connects through the OneDrive integration, because a SuiteFiles workspace is a SharePoint document library. Both have their own setup articles.

Connecting or changing an integration is an Administrator job, so if the settings below aren't available to you, ask an Administrator on your account.

When files are sent

You decide when files leave Content Snare for your drive, and you set this separately for each integration. Pick one trigger:

  • As soon as the client uploads it sends each file the moment your client adds it, and it's the default.
  • When the field is approved waits until you approve the answer the file belongs to.
  • When the entire request is marked as complete holds every file until the request is finished, then queues them.

If a request expires, it is never marked as complete, so the files held for completion are not sent.

Files don't arrive the instant they're uploaded. Content Snare sends them one at a time, so a request with a lot of files takes a little while to appear in your drive.

Where files land

Google Drive and OneDrive/SharePoint put everything into one root folder you pick when you connect. The picker only lists folders that already exist, so create a new empty folder only for Content Snare and select it. Content Snare can't see what's already in the folder you pick. If a subfolder it needs already exists, it uses that one rather than making a new one, so files mix in with work that's already there. A folder of its own avoids that.

Dropbox has no folder picker. It always stores files in its own Apps/Content Snare folder.

Inside the root folder, a path you set decides the subfolders. You build it from placeholders you add with the plus icon: Client Name, Client Company, Request Name, Folder Name and Request Owner. By default the path makes a folder for each client and, inside that, a folder for each request, so files end up organized by client and request automatically. When a request goes to more than one client, Content Snare uses the first client you assigned to fill the Client Name and Client Company placeholders. If one of those values contains a slash, Content Snare turns it into an underscore before it makes the folder.

You can type your own text into the path as well, but keep it to plain words. Letters without accents, numbers and spaces are fine, and so are these characters: _ - ! # $ % & + = @ [ ] ^. Anything else is rejected, such as . , ' ( ) or an accented letter like é.

If you set a naming convention on a question that collects files, Content Snare renames those files to match before they reach your drive.

You can connect one account for each service, so one Google Drive, one Dropbox and one OneDrive or SharePoint. There's no way to point different requests at different Google Drive accounts. To keep clients or jobs separate, use the folder path inside the single account you've connected.

Deleting or replacing a file

Removing a file inside Content Snare doesn't remove it from your drive. Instead, Content Snare renames the copy in your cloud storage to something like invoice-deleted-20260831-141503.pdf and keeps it there. Content Snare never overwrites files in your drive, so when a client replaces a file, both versions stay: the new upload and the earlier one with the -deleted- name. This is why the folder builds up extra files over time.

Automatically export the finished request

Separate from the file triggers, Content Snare can also export a copy of the completed request to your drive. Turn on Export the request when it completes. When a request is marked complete, Content Snare adds a copy of the request to the same folder, as a PDF by default, or as Word, plain text, HTML, CSV or JSON if you prefer. This is the request document, not the files your client uploaded. Complete the request again and Content Snare exports a fresh copy, with a timestamp so the earlier one stays. A request that expires is never completed, so it is not exported.

If you want to export a request yourself rather than on a schedule, including the attachments, see export a request.

Confidential and internal answers

Two settings decide whether confidential and internal content goes to your drive: Include confidential files and answers and Include internal field files and answers. Turn either on to include that content in what Content Snare sends.