Gravity Forms Dropbox Add‑On 3.3.1

I use the Gravity Forms Dropbox Add‑On when the requirement is simple and reliable: “every form submission (especially with file uploads) must end up in Dropbox, organized in predictable folders.” It’s a clean fit for teams already living in Dropbox (legal/HR/intake forms), because it keeps the workflow inside WordPress and avoids extra middleware.

I avoid it when the Dropbox side must enforce complex retention/compliance rules or when uploads are extremely large/high-volume—then I’d rather push files to object storage (S3/R2) and sync downstream, because WordPress upload limits and PHP timeouts become the bottleneck.

How it works (what actually happens on submission)

• The add-on is a Gravity Forms “Feed” integration. You configure one or more Dropbox Feeds per form: which submissions should send, where to store them, and what to name folders/files.
• On submission, it typically hooks into Gravity Forms’ submission lifecycle (commonly around gform_after_submission) and uses the Dropbox API (OAuth) to:
  • create folders (optionally),
  • upload files from File Upload fields,
  • optionally upload a generated file (depends on settings/version),
  • name paths using merged tags / field values.
• Debugging is usually through Gravity Forms Logging:
  • Forms → Settings → Logging (enable logging for the Dropbox add-on and sometimes for Gravity Forms core).

Key implication: the file has to successfully land on your server first (GF upload handling), then it gets pushed to Dropbox. So failures are often either WordPress/PHP upload issues or Dropbox API/auth issues.

Where it usually breaks (root causes + fastest fixes)

1) “Uploads stopped working after it worked once.”
Most common: OAuth token / app authorization issues.

• Reconnect the Dropbox account in the add-on settings (OAuth).
• Confirm the Dropbox app permissions/scopes are still valid and the connected account still has access to the target folder.

2) “Entries submit, but nothing appears in Dropbox (or only sometimes).”
Usually timeouts or request size issues.

• Check server limits: upload_max_filesize, post_max_size, max_execution_time, memory.
• Large files can fail during the server upload phase or during the Dropbox upload API call. If you see inconsistent behavior, test with a small file first to separate “GF upload” from “Dropbox push”.

3) “Folder/file names are weird / upload fails for some entries.”
Often invalid characters or unexpected merge-tag output.

• Remove characters Dropbox doesn’t like in paths, and avoid raw user input in folder names.
• If you build folder paths from multiple fields, test edge cases (empty fields, special characters, very long values).

4) “We changed the form and Dropbox mapping broke.”
Typical field-ID drift (especially when fields are deleted/recreated).

• Reopen the Feed settings, reselect the mapped fields/merge tags, and resave.

[virustotal url=”https://www.virustotal.com/gui/file/3a24718c5701feb8fad87ed63488e732233b88def8271d37cd6c7a7cdead8725″]

Licensing / activation reality (what matters operationally)

This is an official Gravity Forms add-on, so it generally depends on:

• having Gravity Forms installed and active, and
• having the appropriate Gravity Forms license tier for access to the add-on, updates, and support.

Even if everything is working today, plan for updates: Dropbox API/security changes happen, and old add-on versions can break when OAuth policies change.

Installation and activation

Download Gravity Forms Dropbox Add‑On archive with the latest update and install it over the existing version. If there is no previous version installed, the plugin can be installed using the standard method. You can find detailed instructions on how to update a theme or plugin on this page.

FAQ (what I check first)