Introduction
Background or async feed processing is a method that can be used to improve form submission performance.
It does this by moving feed processing to a separate request, which doesn’t block form submission completion, so the form submitter can see the confirmation faster than if they had to wait for the feeds to be processed.
Official Add-Ons
| Add-On | Supported | Enabled |
|---|---|---|
| 2Checkout | No | No |
| ActiveCampaign | Yes | Yes (versions 2.0.1+) |
| Advanced Post Creation | Yes | Yes (versions 1.3.1+) |
| Agile CRM | Yes | Yes (versions 1.4.1+) |
| Akismet | No | No |
| Authorize.net | No | No |
| AWeber | Yes | Yes (versions 2.11.1+) |
| Breeze | Yes | Yes (versions 1.5.1+) |
| Campaign Monitor | Yes | Yes (versions 3.9.1+) |
| Capsule CRM | Yes | Yes (versions 1.6.1+) |
| CleverReach | Yes | Yes (versions 1.7.1+) |
| Constant Contact | Yes | Yes (versions 1.7+) |
| Dropbox | No (1) | No |
| EmailOctopus | Yes | Yes (versions 1.2.2+) |
| Emma | Yes | Yes (versions 1.5.2+) |
| FreshBooks | Yes | No |
| GetResponse | Yes | Yes (versions 1.7.1+) |
| Google Analytics | No | No |
| Help Scout | Yes | Yes (versions 2.1.1+) |
| HubSpot | Yes | Yes (versions 1.8.1+) (2) |
| iContact | Yes | Yes (versions 1.5.1+) |
| Mad Mimi | Yes | Yes (versions 1.4.1+) |
| Mailchimp | Yes | Yes (versions 1.5.1+) |
| Mollie | No | No |
| PayPal Checkout | No | No |
| Slack | Yes | Yes (versions 2.0.1+) |
| Square | No | No |
| Stripe | No | No |
| Trello | Yes | Yes (versions 2.0.1+) |
| Twilio | Yes | Yes (versions 2.9.1+) |
| Zapier | Yes | Yes (versions 4.2.1+) |
| Zoho CRM | Yes | Yes (versions 2.0.1+) |
| User Registration | Yes (3) | Yes (versions 5.0.1+) (4) |
| Webhooks | Yes | Yes (versions 1.0+) |
| Add-On | Supported | Enabled |
Notes
(1) The Dropbox Add-On uses an earlier implementation of background feed processing, so the files are already sent to Dropbox in a separate request that occurs after the submission has completed.
(2) The HubSpot Add-On requires Gravity Forms 2.7.1 or greater to use background feed processing.
(3) Background feed processing can’t be used with the User Registration Add-On when the user is to be logged in automatically by custom code or the Auto Login perk from certified developer Gravity Wiz. Use the gform_is_feed_asynchronous filter to disable it.
(4) Background feed processing for the User Registration Add-On requires Gravity Forms 2.7.1 or greater.
Certified Add-Ons
Below, you will find a list of feed-based add-ons from Certified Developers that are known to support or do not support background processing.
| Add-On | Developer | Supported | Enabled |
|---|---|---|---|
| Easy Passthrough | Gravity Wiz | No | No |
| Entry Automation | CosmicGiant | No | No |
| Fillable PDFs | CosmicGiant | No | No |
| Google Sheets | Gravity Wiz | Yes | Yes |
| Legal Signing | CosmicGiant | No | No |
| Limit Submissions | Gravity Wiz | No | No |
| OpenAI | Gravity Wiz | No | No |
Enabling Background Feed Processing
We are gradually releasing updates to enable background feed processing for add-ons that support it.
If you’d rather not wait for an update to be released, you can update manually using the zip available from the downloads page, or the gform_is_feed_asynchronous filter can be used to enable it.
The filter can also be used to enable it for third-party add-ons that extend the GFFeedAddOn class.
If you’d prefer a third-party add-on used background feed processing by default, please contact the developer and ask if they can set the $_async_feed_processing property, in their class that extends GFFeedAddOn, to true.
Background feed processing might not be suitable for all add-ons. For example, if the add-on relies on submission time hooks or needs to make data available to the confirmation.