Gravity Forms
Overview
AFI creates entries in Gravity Forms from external sources (e.g. inbound webhooks, other forms). Useful for unifying data into a single Gravity Forms entry store, regardless of where the submission originally came from.
Supported actions
- Create Entry — adds a new entry to a specific Gravity Form with all field values populated.
Authentication
- No API key — AFI writes directly to Gravity Forms on the same WordPress install.
- Confirm Gravity Forms is installed and activated.
How to create the integration
- In WordPress admin, go to AFI > New Integration.
- Pick your Sender (Contact Form 7, WPForms, WooCommerce, etc.) and the form / event to listen on.
- Pick Gravity Forms as the Receiver, then pick the Task you want to run.
- Map sender fields onto Gravity Forms’s fields. Form ID + every required field on that form must be mapped.
- Optional: add Conditional Logic so the action only fires on matching submissions.
- Save and run a test submission. Check AFI > Log if anything looks off.
Notes & caveats
- Field IDs vs labels: Gravity Forms uses numeric internal field IDs — AFI fetches the labels to make mapping easier.
- Conditional / hidden fields: the field is created in the entry regardless of conditional visibility.
- Notifications: Gravity Forms admin/user-notifications fire when an entry is created — disable them on the form if you don’t want emails for AFI-created entries.