When new form submission is received in Avada Form, upload the files to Google Drive
When someone submits an Avada form with a file attached, FlowMattic uploads that file to a Google Drive folder you choose, so attachments are kept outside your WordPress site.
Avada Forms
Google Drive2 steps Setup ~5 min Used on 3.0k sites Free to import
What this workflow does
Forms that accept files, such as job applications, design briefs or claim photos, leave those uploads on your web server, where your team has to dig them out. This workflow copies each uploaded file into Google Drive, where it can be shared, organised and backed up with the rest of your documents.
The Avada Forms trigger runs whenever a form built with Avada's form builder is submitted. The submission's fields, including the link to any uploaded file, are passed on.
The Google Drive Upload a File step then sends a file to the Drive folder you select. It ships unmapped: after import, connect your Google account, pick the folder, and map the file from the form's upload field. Submit a test entry with an attachment first, so FlowMattic shows you what the upload field contains.
One Upload a File step handles one file. If your form has two upload fields, add a second Upload a File step for the other one. Each submission makes one run, and Task History shows the file Drive received and its reply.
CVs from a careers page
A recruitment agency's Avada application form takes a CV upload, and each file lands in a Drive folder the hiring team already shares.
Artwork for print orders
A print shop asks customers to upload artwork through an Avada form and keeps every file in Google Drive for the production team.
Photos for warranty claims
A manufacturer collects product photos with warranty claims and stores them in Drive, where support staff can review them with the claim.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Avada Forms New Form SubmissionFires each time an Avada form is submitted on your site. The field values, including the uploaded file's link, become available to map.
- Google Drive Upload a File
Sends the attachment into the Drive folder you pick. The step ships unmapped: connect Google, choose the folder and map the file from the Avada upload field after import.
What you need
- FlowMatticCore
- Avada Forms PluginPlugin
- Google Drive AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- If several Avada forms run on the site, put a Filter between the Avada trigger and the Drive step that matches the form you want. Pick the field that tells forms apart from a test submission.
- Add Google Drive's Share File step after the upload to give a colleague access to each new file by email.
- Add a Slack or email step after the Drive upload to tell your team a new file has arrived, mapping in the sender's name.
Questions about this workflow
What if the Avada form is sent without an attachment?
The workflow still runs, and the Drive step has no file to upload, so Drive may return an error. Put a Filter between the Avada trigger and the Drive step that continues only when the upload field is not empty.
Can I upload several files from one Avada submission?
Each Upload a File step handles one file. Add one step per upload field, or use an Iterator between the trigger and the Drive step if a field holds several files.
Does the file stay on my WordPress site as well?
The workflow copies the file to Drive and doesn't delete anything from your site, so whatever Avada keeps for the entry stays where it is.
More File Management workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted