Pods Gravity Forms Add-On


  • Requires: Pods 3.0+, Gravity Forms 1.9+
  • Demo: Want to try Pods GF out? Check out the Gravity Forms Live Demo and install the Pods and Pods Gravity Forms plugins once you’re there
  • Bugs/Ideas: Please report bugs or request features on GitHub

Special thanks to Rocketgenius for their sponsorship support and to Naomi C. Bush for her help in the initial add-on UI work.

WP-CLI Command for Syncing Entries

This add-on provides the ability to sync entries from a Form Submission and Entry Edit screen. To bulk sync all entries even prior to setting up a Pods Gravity Form Feed, you can run a WP-CLI command.

Example 1: Sync all entries for Form 123 first active Pod feed

wp pods-gf sync --form=123

Example 2: Sync all entries for Form 123 using a specific feed (even if it is inactive)

wp pods-gf sync --form=123 --feed=2

Mapping GF List Fields to a Pods Relationship field

You can map a GF List field to a Relationship field related to another Pod. Using the below examples you can customize how the automatic mapping works. By default, the list columns will map to the pod fields with the same labels.

Example 1: Customize what columns map to which Related Pod fields for Form ID 1, Field ID 2

Customizing a list field row can be done by using the pods_gf_field_columns_mapping filter, which has Form ID and Field ID variations (pods_gf_field_columns_mapping_{form_id} and pods_gf_field_columns_mapping_{form_id}_{field_id}).

add_filter( 'pods_gf_field_columns_mapping_1_2', 'my_columns_mapping', 10, 4 );

 * Filter list columns mapping for related pod fields.
 * @param array    $columns  List field columns.
 * @param array    $form     GF form.
 * @param GF_Field $gf_field GF field data.
 * @param Pods     $pod      Pods object.
 * @return array
function my_columns_mapping( $columns, $form, $gf_field, $related_obj ) {

    $columns[0] = 'first_field';
    $columns[1] = 'second_field';
    $columns[2] = 'third_field';

    return $columns;


Example 2: Customize a List row for Form ID 1, Field ID 2

Customizing a list field row can be done by using the pods_gf_field_column_row filter, which has Form ID and Field ID variations (pods_gf_field_column_row_{form_id} and pods_gf_field_column_row_{form_id}_{field_id}).

add_filter( 'pods_gf_field_column_row_1_2', 'my_column_row_override', 10, 6 );

 * Filter list field row for relationship field saving purposes.
 * @param array      $row         List field row.
 * @param array      $columns     List field columns.
 * @param array      $form        GF form.
 * @param GF_Field   $gf_field    GF field data.
 * @param array      $options     Pods GF options.
 * @param Pods|false $related_obj Related Pod object.
 * @return array
function my_column_row_override( $row, $columns, $form, $gf_field, $options, $related_obj ) {

    // Update certain row fields based on the value of specific column.
    if ( ! empty( $row['user_relationship_field'] ) ) {
        $user = get_userdata( (int) $row['user'] );

        // Set the post_title to match the User display name.
        if ( $user && ! is_wp_error( $user ) ) {
            $row['post_title'] = $user->display_name;

    return $row;


Fota wobrazowki

  • In the Pods Admin, create your Pods and Pod Fields: Pods Admin -> Add New
  • In the Pods Admin, create your Pods and Pod Fields: Pod Edit Screen
  • Create your Gravity Form that will be used to create a Pod item
  • Form Settings->Pods menu
  • Pods feed page
  • Map form fields to Pod fields
  • Example form
  • New Pod item created from form submission
  • Form entries page showing Pod ID


1. meje 2020
The capabilities of this plugin in linking pods with gravity forms is enormous. Boundless possibilities with passing data between pods and gravity forms.
3. měrca 2020
Easy to use and work with! Just what I needed! You can reload a gravity form after submission by putting a special gravity form link called referrer in the link to field post submission. I do hope that gravity forms adds ajax submission in the future so that I can stay on the page without needing to reload the whole page.
28. septembra 2017
Easy and powerful way to feed pods via frontend forms. Even complex forms up & running within minutes … excellent. Thanks guys.
10. junija 2017
Makes Connecting Pods to GF an easy Task especially with the improvements from the last release!
Čitajće 7 pohódnoćenjow

Sobuskutkowarjo a wuwiwarjo

„Pods Gravity Forms Add-On“ je softwara wotewrjeneho žórła. Slědowacy ludźo su k tutomu tykačej přinošowali.


Protokol změnow

1.5.0 – March 29th, 2024

  • New requirements that match Pods: WP 6.0+, PHP 7.2+, and Pods 3.0+ to prep for Pods Gravity Forms 2.0 (@sc0ttkclark)
  • Added: Support value overrides for checkbox GF fields when prepopulating. (@sc0ttkclark)
  • Added: Allow for passing ?pods_gf_debug=1 to a form submit URL to debug the form submission mapping to Pods which outputs debug information and stops before the save runs). (@sc0ttkclark)
  • Added: New hook pods_gf_dynamic_select_show_empty_option lets you disable showing the „empty option“ in dynamic fields being prepopulated. (@sc0ttkclark)
  • Added: New hook pods_gf_addon_options_{$form_id} that lets you filter the options built for a feed for the Pods_GF object. (@sc0ttkclark)
  • Tweak: New pods-gf-ui-view-only class added to the view-only mode. (@sc0ttkclark)
  • Tweak: Expanded secondary submit handling with the ability to have cancel button. (@sc0ttkclark)
  • Fixed: Resolved various PHP notices. (@sc0ttkclark)
  • Fixed: Removed „comments“ from the field mapping options in the feed. (@sc0ttkclark)
  • Fixed: Remove extra HTML in the feed labels. (@sc0ttkclark)
  • Fixed: For non-select GF field types, trim the dashes on the custom select_text option used. (@sc0ttkclark)
  • Fixed: Prepopulating field values works more consistently now when passing the prepopulated filter pre-chunked arrays of values. (@sc0ttkclark)
  • Fixed: View-only mode forced to use page zero. (@sc0ttkclark)
  • Fixed: Prevent duplicate submissions during feed processing. (@sc0ttkclark)
  • Fixed: Only allow working with active leads in Pods_GF_UI. (@sc0ttkclark)
  • Fixed: Prevent Markdown conflicts with other plugins and update PHP 8 compatibility by switching to the Parsedown library. #166 (@sc0ttkclark)
  • Fixed: Stop prepopulating fields that aren’t opted-in to it. #168 (@sc0ttkclark)

ALSO: Pods Gravity Forms 2.0 is still in development and it brings complete compatibility with the latest Gravity Forms releases. We could use your support to help it get over the finish line this year. Please consider donating to the Pods project to help us get there more quickly.

1.4.5 – July 22nd, 2022

  • Tested against WP 6.0
  • Added: Not seeing something map correctly? As a site admin, you now have the power to debug the form submission and see what might be going on. Add ?pods_gf_debug_gf_to_pods=1 to the URL of the form action before submitting to take advantage of the admin-only debug mode. This will output the values as they would be sent to Pods, the entry information used to reference it, and the feed options used at the time. It will stop the form from completely saving to Pods so you can tweak and debug your form feeds however much you’d like to perfect them. (@sc0ttkclark)
  • Fixed: Conditional checks for feeds has been resolved and now won’t get confused when there are multiple feeds for the same form in certain cases. (@sc0ttkclark)
  • Fixed: Additional compatibility with Gravity Flow. #157 (@JoryHogeveen)
  • Pods 2.9 is in beta and after it is released, new mapping of GF List Fields to Pods repeatable fields will be added. This add-on will also be updated with minimum version requirements updated for WP 5.5+, Pods 2.8+, and Gravity Forms 2.5+. Complete testing will be done at that time to ensure complete compatibility.

1.4.4 – October 6th, 2021

  • Tested against WP 5.8
  • Get ready for Pods 2.8 in just a week! This add-on will receive updates to ensure it is compatible with the latest Gravity Forms and the changes in Pods 2.8

1.4.3 – March 26th, 2020

  • Added: Now requiring PHP 5.4+
  • Added: Freemius support when running Pods 2.7.17
  • Fixed: Prepopulate handling for relationship fields.
  • Fixed: Prevent errors when form doesn’t exist by the time it gets to our hook.

1.4.2 – March 2nd, 2020

  • Fixed: Ajax handling for various callbacks that hook into gform_pre_render.
  • Fixed: Cleaned up logic and prevent PHP notices with multi-select arrays when setting up choices arrays.
  • Fixed: Make sure Pods_GF_UI does not return false on UI callbacks to prevent access errors.
  • Fixed: Add mapping feeds to the import/export! (props @travislopes)

1.4.1 – October 16th, 2018

  • Fixed: When syncing multiple entries, the field values were caching and not unique per entry resulting in what appeared to be duplicated content inserts/updates.

1.4 – October 16th, 2018

  • Support: Added support for Gravity Forms 2.3 database tables changes (You may see a warning on the Edit Pod screen but this is a false positive because we cache a list of all tables to transients and it triggers the warning solved by removing those old „rg“ tables)
  • Changed: Backwards compatibility issue — You can now more easily set custom override values, however the old style was not able to be brought over — you’ll want to update your feeds when possible, the old values will not show up and you’ll have to select the custom override value option once more, then fill it in
  • Changed: Backwards compatibility issue — Now requiring WordPress 4.6+
  • Feature: When editing entries in the admin area, changes now sync to the associated Pod item (except trash/deletes)
  • Feature: New Bulk Entry Syncing to Pods WP-CLI command wp pods-gf sync --form=123 or you can specify which feed (even if it is not active) with wp pods-gf sync --form=123 --feed=2
  • Feature: Support for List field mapping to a Pod field which ends up serializing the value, but can be prepopulated back into the Gravity Form
  • Feature: List field mapping to relationship fields related to another Pod (list columns map to individual fields in the related Pod) with new filters pods_gf_field_columns_mapping and pods_gf_field_column_row
  • Feature: Support for Chained Select field mapping to a Pod field
  • Feature: New Custom fields section added for Pods that support meta (Posts, Terms, Users, Media, and Comments), you can set additional custom fields including ability to set custom values there too
  • Feature: Ability to set conditional processing per feed, based on specific values submitted
  • Added: Whenever you create a new feed, mapping will automatically be associated between a Gravity Form field and a Pod field if the labels match
  • Added: Custom override values now support GF merge tags by default (no insert UI yet) like {form_id} and any other merge tag
  • Added: Required WP Object Fields in mapping are no longer required if you choose to ‚Enable editing with this form using ____‘ option for Post/Media or User pod types
  • Added: Support for E-mail field mappings with ‚Confirm E-mail‘ enabled
  • Added: Support for Date fields with multiple inputs (date dropdown / text fields)
  • Added: Smarter requirement handling for WP object fields based on object type (only require what the WP insert API requires)
  • Added: New mapping fields are now available for more Entry and Payment fields
  • Added: New merge tags {pods.id} and {pods.permalink} are available for usage and in the merge tag selection dropdowns
  • Improved: Added headings to each group of feed options so they are easier to work with
  • Improved: Address field mapping for Country, State, and CA Provinces now convert properly to their Pods counterparts
  • Updated: PHP Markdown library updated to 1.0.2
  • Fixed: Issues with using ‚bypass‘ as a save action
  • Fixed: Dynamic select options should set the current value (as posted in form) properly
  • Fixed: Date/time fields shouldn’t auto populate with empty dates such as 0000-00-00 anymore
  • Fixed: Additional attachment processing fixes
  • Fixed: Lots of Pods GF UI issues resolved
  • Fixed: Removed Autocomplete limit (was 30) that was being enforced, now all data from related field will show
  • Fixed: Dynamic mapping value checking to support arrays of values
  • Fixed: Lots of Prepopulating fixes
  • Fixed: Now supports multi page form validation and prepopulating