Zapier allows you to quickly connect popular, cloud-based apps to the Widen Collective to automate file uploads. You can create a zap to connect the two apps, allowing you to complete an action in one app - a trigger app - and a resulting action occurs in another app -- an action app. Apps like Box, Dropbox, Instagram, Gmail, Evernote, and Google Drive, as well as many others, are trigger apps. The Collective is an action app that triggers a file to be automatically uploaded.
Use of Zapier automates the upload of files from other apps into your Collective site to ensure valuable files are centralized. Once project files are approved in Basecamp, for example, set up a zap to upload to a specific upload profile in the Collective. Capture user-generated content through Instagram and send it directly to the Collective to repurpose.
Depending on your account level in Zapier, the file upload process occurs in intervals of 15 minutes or less.
To send files to the Collective from another app, create a zap between a trigger app and the Collective. After it's created, you can quickly upload from that app to the Collective. Create as many zaps as allowed by the Zapier plan you choose.
For example, you can create a zap between Dropbox and the Collective. When a new file is added to your Dropbox directory, the file will be automatically uploaded to the Collective.
Set up a Collective asset
When creating a zap, you'll set up a Collective asset. To do that, select an upload profile from the list of those available in the Collective, choose a filename (folder), and choose the file to upload. The filename is a list of folders in the trigger apps. Once the filename is chosen, choose from the list of available files in the trigger app.
Apps are connected from Zapier to the Collective when a zap is created. If you have permission to upload in the Collective, upload profiles display for you to as the target for the zap.
Only a single upload profile can be selected as a target for each zap; however, you can set up as many zaps as you need to support workflows and ensure files are placed in the appropriate upload profiles and tagged with the appropriate metadata.
An example workflow in Basecamp is, after approval, files can be automatically uploaded to the Collective with the default metadata that has been set for the upload profile. Whatever metadata is included in the profile will be used to automatically tag the file when it’s uploaded to the Collective.