This plugin hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Gravity Forms Salesforce Add-on

Description

This is the best WordPress Salesforce plugin.

Integrate Your Forms with Salesforce

Add one setting, check a box when configuring your forms, and all your form entries will be added to Salesforce from now on. Integrating with Salesforce has never been so simple.

Gravity Forms + Salesforce = A Powerful Combination

This free Salesforce Add-On for Gravity Forms adds contacts into Salesforce automatically, making customer relationship management simple. The setup process takes a few minutes, and your contact form will be linked with Salesforce.

Read the FAQ for information on how to integrate with Custom Fields.

Using the API

The Gravity Forms Salesforce API Integration requires PHP 5.3 or higher.

If you have the following Salesforce Editions, you can use the included API Add-on:

  • Enterprise Edition
  • Unlimited Edition
  • Developer Edition

If you use the following Editions, you will use the included Web-to-Lead Add-on:

  • Personal Edition
  • Group Edition
  • Professional Edition
    Note: You can also purchase API access for a Professional Edition.

Web to Case

When using the Web-to-Lead Add-on, you can choose to have form entries sent to Salesforce as Cases (like when using the Web-to-Case form) instead of as Leads.

If you have questions, comments, or issues with this plugin, please leave your feedback on the Plugin Support Forum.

Want to help translate?

The plugin fully supports multiple languages! Please help translate the plugin!

Screenshots

  • Configure Salesforce field mapping. Set up custom objects.
  • Integrate with more than one form.
  • Salesforce.com settings page
  • Web-To-Lead: View of Form Feeds. You can have multiple feeds for each form.
  • Web-To-Lead: View of the Web-To-Lead Settings screen.
  • Web-To-Lead: You can easily configure the field mapping for export to Salesforce using Feeds.
  • Web-To-Lead: The plugin integrates with the Gravity Forms Logging Tool to log all activity and/or errors.
  • Web-To-Lead: Specify custom fields and use the Salesforce API ID to send additional data to Salesforce.
  • Daddy Analytics Integration: The plugin integrates with Daddy Analytics
  • The Add-on loader added in version 3.0: Choose between API or Web-to-Lead Add-Ons.
  • Form Feeds can have rich mapping relationships: An Entry can create a Contact, which is then assigned to an Opportunity and is also assigned an Opportunity Contact Role.
  • The mapping of the Opportunity Contact Role shows the rich object mapping in action.

Installation

  1. Upload plugin files to your plugins folder, or install using WordPress’ built-in Add New Plugin installer
  2. Activate the plugin
  3. Go to the plugin settings page (under Forms > Settings > Salesforce Add-on )
  4. Choose your Integration Method (API or Web-to-Lead)

API

  • Select API as your Integration Method
  • Click Save Settings.
  • Click the “Salesforce: API” menu in the current settings
  • Click the “Login with Salesforce” button
  • Log in to Salesforce.com
  • Click on the Forms > Salesforce menu link to create a feed
  • Follow the steps to create a feed

Web-to-Lead

  • Select Web-to-Lead as your Integration Method
  • Click Save Settings
  • Go to the Gravity Forms Forms page (the Forms menu)
  • Edit the form you want to connect with Salesforce
  • On the Edit Form page, under “Form Settings”, click the “Salesforce: Web-to-Lead” link
  • Click the link to create a feed

If you are using the Web-To-Lead Add-on you must have Web-To-Lead enabled. Read how to enable Web-to-Lead on Salesforce.com.

FAQ

Installation Instructions
  1. Upload plugin files to your plugins folder, or install using WordPress’ built-in Add New Plugin installer
  2. Activate the plugin
  3. Go to the plugin settings page (under Forms > Settings > Salesforce Add-on )
  4. Choose your Integration Method (API or Web-to-Lead)

API

  • Select API as your Integration Method
  • Click Save Settings.
  • Click the “Salesforce: API” menu in the current settings
  • Click the “Login with Salesforce” button
  • Log in to Salesforce.com
  • Click on the Forms > Salesforce menu link to create a feed
  • Follow the steps to create a feed

Web-to-Lead

  • Select Web-to-Lead as your Integration Method
  • Click Save Settings
  • Go to the Gravity Forms Forms page (the Forms menu)
  • Edit the form you want to connect with Salesforce
  • On the Edit Form page, under “Form Settings”, click the “Salesforce: Web-to-Lead” link
  • Click the link to create a feed

If you are using the Web-To-Lead Add-on you must have Web-To-Lead enabled. Read how to enable Web-to-Lead on Salesforce.com.

Web-to-Lead: DateTime fields don’t process

This is a known issue. We’ve tried everything to get this working, but Salesforce won’t accept any submitted DateTime formats.

Here’s how to enable the functionality. If you find a solution, let us know on that page.

Web-to-Lead: I’m not seeing any errors, but the entry didn’t get added to Salesforce!

Please check the box “Enable Salesforce debugging emails” in the Web-to-Lead settings page. Salesforce will send you an email with a reason the lead or case wasn’t added.

Web-to-Lead: How do I convert my existing form configuration to Feeds?

See “Web-to-Lead: How do I create a Feed” below.

API: How do I create a Feed?
  • Go to the plugin settings page (under Forms > Settings > Salesforce Add-on )
  • Choose your Integration Method (API or Web-to-Lead)
  • Select API as your Integration Method
  • Click Save Settings.
  • Click the “Salesforce: API” menu in the current settings
  • Click the “Login with Salesforce” button
  • Log in to Salesforce.com
  • Click on the Forms > Salesforce menu link to create a feed
  • Follow the steps to create a feed
Web-to-Lead: How do I create a Feed?

To create a feed:

  • Go to the plugin settings page (under Forms > Settings > Salesforce Add-on )
  • Select Web-to-Lead as your Integration Method
  • Click Save Settings
  • Go to the Gravity Forms Forms page (the Forms menu)
  • Edit the form you want to connect with Salesforce
  • On the Edit Form page, under “Form Settings”, click the “Salesforce: Web-to-Lead” link
  • Click the link to create a feed
Web-to-Lead: How do I modify the debug email address?

The Salesforce debugging emails are sent to the website administrator by default. To modify this, add a filter to gf_salesforce_salesforce_debug_email_address that returns an email address.

Web-to-Lead: How do I add an entry to a Campaign?

To associate a Web-to-Lead with a Campaign, you must also set the “Member Status”. Read the Salesforce help article

  • Add two fields to your form:
    1. “Campaign ID” – The “Campaign ID” form field will be a hidden field. Add a hidden field, click the “Advanced” tab, and add the ID of the Campaign you want to add the entry to (it will look something like 902A0000000aBC1). For Advanced Users: Alternately, you can make this form a Radio Button field with different Campaign IDs values for different options.
    2. “Member Status” – Your campaign has different statuses for campaign members, such as “Sent” and “Responded”. You can either create a hidden field with a pre-determined value, or a Radio Button field with different status options. The values should match up with your Salesforce Campaign Status options.
  • Save the form
  • Go to Form Settings > Salesforce: Web-to-Lead
  • Create a Feed or edit an existing Feed (see “Web-to-Lead: How do I create a Feed?” above for more information)
  • Find the “Campaign ID” row and select the Campaign ID field you just created
  • Find the “Member Status” row and select the Status field you just created
  • Save/Update the Feed.
  • There you go!
Web-to-Lead: My input values are being cut off in Salesforce

If you are submitting to a “Multi PickList” field in Salesforce, the values need to be separated with ‘;’ instead of ‘,’. Add a filter to your functions.php file:

add_filter('gf_salesforce_implode_glue', 'change_salesforce_implode_glue');

/**
 * Change the way the data is submitted to salesforce to force submission as multi picklist values.
 * @param  string $glue  ',' or ';'
 * @param  array $field The field to modify the glue for
 * @return string        ',' or ';'
 */
function change_salesforce_implode_glue($glue, $field) {

    // Change this to the Salesforce API Name of the field that's not being passed properly.
    $name_of_sf_field = 'ExampleMultiSelectPicklist__c';

    // If the field being checked is the Salesforce field that is being truncated, return ';'
    if($field['inputName'] === $name_of_sf_field || $field['adminLabel'] === $name_of_sf_field) {
        return ';';
    }

    // Otherwise, return default.
    return $glue;
}
How do I modify the Soap, Proxy, WSDL and connection settings?
  • gf_salesforce_wsdl – Path to the WSDL (string)
  • gf_salesforce_proxy – Proxy settings as an object with properties host, port (integer, not a string), login and password (object, ideally a ProxySettings object)
  • gf_salesforce_soap_options Additional options to send to the SoapClient constructor. (array) See http://php.net/manual/en/soapclient.soapclient.php
  • gf_salesforce_connection – Modify the SforcePartnerClient object before it’s returned.

See the FAQ item above for an example of using a filter.

Do I need both plugins activated?

No, you only need one, and the API plugin is recommended: the Web-to-Lead plugin is no longer being actively developed. If you are using Web-to-Lead, you don’t need the API plugin activated. If you are using the API plugin, you don’t need the Web-to-Lead activated.

What are the server requirements?

Your server must support the following:

  • PHP 5.x
  • SOAP Enabled
  • SSL Enabled
  • cURL Enabled
  • OpenSSL Enabled
I have Salesforce Enterprise Edition, not Partner Edition

Add the following to the bottom of your theme’s functions.php file, before ?>, if it exists:

add_filter('gf_salesforce_enterprise', '__return_true');
How do I set a custom Lead Source? (Web-to-Lead)

This feature support was added in version 1.1.1. gf_salesforce_lead_source is the filter.

Add the following to your theme’s functions.php file. Modify as you see fit:

add_filter('gf_salesforce_lead_source', 'make_my_own_lead_source', 1, 3);

function make_my_own_lead_source($lead_source, $form_meta, $data) {
    // $lead_source - What was about to be used (normally Gravity Forms Form Title)
    // $form_meta - Gravity Forms form details
    // $data - The data passed to Salesforce

    return $lead_source; // Return something else if you want to.
}
My Assignment Rule is not triggered. How do I fix this?

add_action(‘gf_salesforce_connection’, ‘gf_salesforce_set_default_assignement_rule’);

function gf_salesforce_set_default_assignement_rule($client) {
    //  Two Options for Setting Assignment Rule
    //    1.  Pass in AssignmentRule ID and "false" to use a specific assignment rule.
    //    2.  Pass in null and true to trigger the DEFAULT AssignementRule
    $header = new \AssignmentRuleHeader(null, true);

    $client->setAssignmentRuleHeader($header);

    return $client;
}
Can I use Salesforce Custom Fields? (Web-to-Lead)

You can. When you are trying to map a custom field, you need to set either the “Admin Label” for the input (in the Advanced tab of each field in the Gravity Forms form editor) or the Parameter Name (in Advanced tab, visible after checking “Allow field to be populated dynamically”) to be the API Name of the Custom Field as shown in Salesforce. For example, a Custom Field with a Field Label “Web Source” could have an API Name of SFGA__Web_Source__c.

You can find your Custom Fields under [Your Name] → Setup → Leads → Fields, then at the bottom of the page, there’s a list of “Lead Custom Fields & Relationships”. This is where you will find the “API Name” to use in the Admin Label or Parameter Name.

If that doesn’t work
If the fields are not submitting properly still, you may need to try a different approach: under “Lead Custom Fields & Relationships”, click on the name of the field. The URL of the page you go to will be formatted like this: https://na123.salesforce.com/12AB0000003CDe4?setupid=LeadFields. You want to copy the part of the URL that looks similar to 12AB0000003CDe4. Use that value instead of the API Name.

I need to send a “Date/Time” field, not a “Date” field. How do I do that? (Web-to-Lead)

Salesforce makes this a little difficult, sorry!

You need to add the following to your theme’s functions.php file:

add_filter('gf_salesforce_use_datetime', 'filter_the_gf_salesforce_datetime', 10, 3);

/**
 * Modify whether to use Date/Time format instead of Date based on the field key.
 * @param  boolean $use_datetime Whether to use Date/Time.
 * @param  string  $key          Key of field.
 * @param  array   $vars         Array of relevant data: 'form', 'entry', 'field', 'feed'
 * @return boolean               True: Use "Date/Time" format; False: use "Date" format
 */
function filter_the_gf_salesforce_datetime($use_datetime = false, $key = '', $vars = array()) {

    // CHANGE THE NAME BELOW to the field name you want to use Date/Time for!
    if($key === 'MY__Custom_DateTime_Key') { return true; }

    // If it's not a match, use default (Date)
    return $use_datetime;
}

If that doesn’t work, you can modify the format for the date by using this code:

add_filter('gf_salesforce_format_date', 'modify_gf_salesforce_format_date');

/**
 * The default is US-style,  though Salesforce recommends Y-m-d\'\T\'H:i:s
 * You can use any date formatting as shown here:
 * @link  http://php.net/manual/en/function.date.php
 */
function modify_gf_salesforce_format_date($previous = '') {
    $date_format = 'Y-m-d\'\T\'H:i:s';
    return $date_format;
}
I know I have SOAP enabled and the API plugin says I don’t.

Add this to the bottom of your theme’s functions.php file to force loading even if a SOAPClient class does not exist:

add_filter( 'gf_salesforce_soap_is_available', '__return_true');
Checkboxes aren’t being passing to Salesforce

Make the value of checkboxes 1 in Gravity Forms. See how to do that here.

What’s the license for this plugin?

This plugin is released under a GPL license.

Reviews

Not updated enough

The plugin author has not updated the plugin in over 2 years. They have a message pinned up to the support forum from 7 months ago that the plugin is being updated, but not progress has been seen on that.

SalesForce has a critical update needed to the plugin for those that need the TLS 1.1 update for the web-to-lead or web-to-case integration.

Great For Small Nonprofit

Love this little plupin. Our small non-profit has a couple of staff members, so we are moving to as much automation as possible. This Plugin is just the ticket.

Not working and not seeing much support

This would be an awesome plugin however I can’t even get the tab to show up on the form to use it and this seems like a common issue in the support threads with no developer around to help solve it.

Read all 22 reviews

Contributors & Developers

“Gravity Forms Salesforce Add-on” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

3.1.2

  • Added: Web-to-Lead setting to choose date formats for date fields (mm/dd/YYYY or dd/mm/YYYY)
  • Added: gravityforms_salesforce_object_added_updated action after entry is added or updated in Salesforce using the API
  • Fixed: Gravity Forms warnings in admin
  • Fixed: Link to API settings when in API Feed configuration

3.1.1 (February 17, 2015)

  • Fixed: Warning in Gravity Forms 1.9 about Add-on requiring an update
  • Fixed: Loading order of settings tabs

3.1 (December 1, 2014)

  • Thank you to @zmonteca for this update. The great new functionality was added by him!
  • Added: Use of Sandbox constant
  • Fixed: Whitespace consistency
  • Fixed: Lots of logging updates for verbosity
  • Fixed: Do not process inactive feeds
  • Fixed: Ability to sort the order of feeds list
  • Fixed: Feed select boxes are all sorted alphabetically now
  • Fixed: Localization functionality – added Text Domain information
  • Added: Romanian translation – thanks @ArianServ!
  • Added: Feed Primary Keys can now be used to update previous records properly.
    • For example, “Form A” has two SF tables worth of data — Contact & Address. You can create an Address feed and a Contact feed. If the Address feed is ordered before the Contact feed in the feed list, you can use the Contact feed’s Primary Key to map to the Address Primary Key. This is helpful to map true relationships in Salesforce.
  • Added: Any feed can map foreign keys to Primary Keys, thus mapping rich relationship in SF.
    • For example, Form B has five dependent Salesforce tables worth of data — Contact, Opportunities, Opportunity Contacts, Contact, Tribute. Now you can create a Contact, have it linked to Opportunities. But also create a second Contact and map that as well as the Opportunity to a custom Tribute table. It’s very fancy – see the Frequently Asked Questions for more information.

3.0.6.3 (September 12, 2014)

  • Fixed: Removed field var_dump

3.0.6.2 (September 5, 2014)

  • Fixed: Issue saving Web-to-Lead settings for Gravity Forms 1.8.10 or higher. Thanks, @twiginteractive
  • Fixed: An issue with the OAuth library clashing if the same library is used elsewhere. Thanks, @JasonTheAdams
  • Confirmed compatibility with WordPress 4.0

3.0.6.1 (August 18, 2014)

  • If you haven’t read the 3.0.5 notes, please do so!
  • Fixed: Issue with refreshing Salesforce authorization token

3.0.6 (July 19, 2014)

  • If you haven’t read the 3.0.5 changelog notes, please do so!
  • Added: Enabled Merge Tag field value support (issue #97)
  • Added [API Add-on]: “Form Title” as an option for mapping form fields
  • Fixed: Form details were not being properly passed (issue #94)
  • Fixed: DaddyAnalytics API names were incorrect for the API integration
  • Fixed: PHP warning about calling static functions
  • Added: Additional Debugging

3.0.5 (June 26, 2014)

  • !!MAJOR UPDATE!! Please read through the changes below.
  • API Add-on Changes
    • You will need to update your settings after installing the plugin.
    • The Add-on no longer requires your Salesforce Security Token and Email.
    • The API Add-on now REQUIRES PHP 5.3 If your website is running PHP 5.2, the API plugin will no longer work. This is necessary to improve security.
    • Added debug and error logging support (using the Gravity Forms Logging Tool)
  • Web-to-Lead Add-on
    • Now supports mapping Address 2 fields
    • Fixed issue with some leads not being added; this was likely because of the time it took to submit a lead to Salesforce.
  • Daddy Analytics integration – the Add-on now works great with Daddy Analytics. What is Daddy Analytics? It allows you to track your leads from their original source, and with that information, you can get true marketing ROI.
  • Changed how the plugins are loaded – there’s now a “Salesforce” setting in the Gravity Forms Settings page. Go there to enable or disable the different plugins. There are no longer multiple visible plugins for this Add-on.
  • Added translation If you want to help translate the plugin, please submit your translation here](https://www.transifex.com/projects/p/gravity-forms-salesforce-add-on/).

3.0.4 (June 26, 2014)

  • Fixed: Threw invalid API warning if settings hadn’t been saved.
  • Added: Localization strings
  • Fixed: Both Integration Methods were showing in the Settings menu

3.0.3 (June 20, 2014)

  • Fixed: Finally nailed the OAuth Refresh Token flow. It’s all working nicely now.

3.0.2 (June 4, 2014)

  • Fixed: is_plugin_active() not defined fatal error on activation

3.0.1 (May 11, 2014)

  • Modified: Hide Daddy Analytics custom API Name settings, unless the gf_salesforce_custom_da_api_names filter returns true.
  • Fixed (API): Return false in get_api() method when settings are empty.

2.6.4.1 (March 19, 2014)

  • Fixed (API Version): Entry update improvement when set to manually export to Salesforce
  • Removed: Unused plugin-upgrade.php file

2.6.4 (February 20, 2014)

  • Fixed (API Version): Live Remote Field Mapping improvements
    • Fixed endless spinning
    • Empty options are better managed; shows “No Picklist Fields” message
    • Now shows an error message if the field cannot be used for Remote Field Mapping
    • Static PHP warning fixed when WP_DEBUG enabled

2.6.3.4 (February 20, 2014)

  • Added (API Version): new hook “gf_salesforce_show_manual_export_button” to disable “send to salesforce” button/checkbox

2.6.3 to 2.6.3.3 (February 14, 2014)

  • Web-to-Lead: Re-added the functionality to show the “Salesforce enabled” icon in the forms list that indicate active feeds are enabled for that form.
    • Integrated that method into the KWSAddon class
  • Web-to-Lead: HotFix: Check for correct Add-on class name (KWSGFAddOn2_1)
  • Web-to-Lead: Fix: show multiple “Salesforce enabled” icons in the forms page

2.6.2 (February 11, 2014)

  • API Version: Added a check to make sure server supports SOAP
  • API Version: Added a filter to override the SOAP check. Use add_filter( 'gf_salesforce_soap_is_available', '__return_true'); to force loading even if a SOAPClient class does not exist.

2.6.1.1 (February 6, 2014)

  • Added: Add a new filter gf_salesforce_format_date to change date format for Date field type before exporting to Salesforce

2.6 & 2.6.1 (January 23, 2014)

  • Added: Manual export of leads – a new setting in the Form settings configuration that prevents all entries from being sent to Salesforce; only manually-approved entries may be sent.
  • Added: $feed and $api variables into the gf_salesforce_create_data filter, so that additional things can be done in $merge_vars based on the feed options, and $api can be further tweaked (setAssignmentRuleHeader) based on the feed object name. Thanks, @sc0ttkclark!
  • Fixed: PHP static method warnings
  • Fixed: Supports paths outside of standard WP plugin directory structure

2.5.3

  • Fixed: Minor PHP static method warning
  • Fixed: Dates now export properly in API and new Web-to-Lead Addon

2.5.2.1

  • Fixed: Minor PHP static method warning

2.5.2

  • Added “Upsert” functionality – if an object (Lead or Contact for example) already exists in Salesforce, update it rather than creating another object. Configure this setting at the bottom of existing Feeds.

2.5 & 2.5.1 on January 7, 2014

  • Web-to-Lead: Completely re-wrote the add-on to provide full Feed capability. See the FAQ to learn how to set up the new feeds: “Web-to-Lead: How do I convert my existing form configuration to Feeds?” (Requires Gravity Forms 1.7+)
  • Web-to-Lead: Added integration with the Gravity Forms Logging Tool
  • Web-to-Lead: Added option for Salesforce debugging emails, which are very helpful!
  • API: Added a filter gf_salesforce_enterprise to use the Enterprise Client instead of the Partner client. Thanks, @sc0ttkclark

2.4.1

  • Added more filters: gf_salesforce_mapped_field_name, gf_salesforce_mapped_value, gf_salesforce_mapped_value_{$field_name}. Thanks, @sc0ttkclark!

2.4

  • Added filters to modify connection details. See the FAQ item “How do I modify the Soap, Proxy, WSDL and connection settings?”
  • Updated to latest Salesforce PHP Toolkit library

2.3 & 2.3.1 & 2.3.2

  • API
    • Now fully supports custom objects!
    • Fixed error with endless spinning when choosing “Select the form to tap into”
    • Fixed a few PHP notices
    • Now supports line breaks in submitted content
  • Web to Lead
    • Fixed issue on Form Settings page caused by Gravity Forms 1.7.7 update.
    • Now properly handles data with ' and " – no longer adds slashes

2.2.7

  • Updated Web to Lead
    • Fixed Lists input type
    • Fixed issue where checkboxes and multiselects were being added as Array

2.2.6

  • Updated Web to Lead to work with Gravity Forms 1.7+ form settings screens

2.2.5

  • Fixed Web to Lead picklist functionality. Thanks, Ryan Allen!

2.2.4.3

  • Fixed issue that should never have happened, but did: the “Gravity Forms Not Installed” message showed up for an user on the front-end of their site and prevented them from logging in.
  • Fixed admin PHP Notice when gravity forms is not activated

2.2.4.2

  • Fixed one more issue with “Array” as submitted value when using select dropdown lists and Salesforce Field Mapping. Note: after updating the plugin, you may need to re-save your affected forms.

2.2.4.1

  • Fixed issue introduced in 2.2.4 that prevented options from being editable when Salesforce Field Mapping was not enabled.

2.2.4

  • Fixed issue with selecting Live Field Mapping where object information wouldn’t load if there was an apostophe in the field name or description.
  • Improved Live Field Mapping display: disabled fields stay looking disabled on form save.
  • Fixed issue where Live Field Mapping would not send form data properly. This was caused by the plugin wrongly assigning “inputs” to the fields, causing the field IDs not to match upon submit.
  • Fixed version number on Gravity Forms Salesforce Web to Lead Add-On so that it won’t always seem like there’s an update waiting.

2.2.3

  • Fixed issue where Web to Lead Form Editor would no longer load if Salesforce API plugin was enabled and not configured. As reported here and here.
  • Fixed issue where Salesforce Fields disappeared when mapping fields using the Salesforce API plugin, as reported here. Thanks to @gmcinnes for the fix.
  • Improved XML validation by escaping XML characters < ' " & > and also removing UTF-8 “control characters”. Should solve the issue reported here in regards to “PHP Fatal error: Uncaught SoapFault exception: [soapenv:Client] An invalid XML character (Unicode: 0xb) was found in the element content of the document.”

2.2.2

  • Added Edit Form and Preview Form links to Salesforce.com Feeds list
  • Fixed issues with array processing with new _remove_empty_fields and _convert_to_utf_8 methods

2.2.1

  • API: Made live updating optional with radio button
  • API: Added cache time dropdown
  • API: Refreshes transients when changing cache time
  • Web to Lead: Fixed issue where Salesforce icon wouldn’t show up on load in Edit Form screen
  • Web to Lead: Salesforce icon now shows properly on Edit Forms screen

2.2

2.1.1

2.1

  • Fixed: Added support for multiselect fields other fields with multiple responses
  • Added: Entries now get assigned a Salesforce ID that link directly to the Salesforce contact or object (API plugin only)
  • Added: Notes are now added to Entries with the success or error messages from exporting to Salesforce (API plugin only)
  • Added: You can have Salesforce export errors emailed to you when they occur (API plugin only)

2.0.2

2.0.1

  • Renamed the plugin files so that you wouldn’t need to re-activate.

2.0

  • Added API plugin. A complete rewrite; switched to SOAP API. Will require re-configuring the plugin.
  • Renamed 1.x plugin “Gravity Forms Salesforce Web to Lead Add-On”

1.1.3

  • Fixed issue with latest Gravity Forms preventing Salesforce checkbox from showing up – thanks Michael Manley!

1.1.2

  • Fixed issue where entered Salesforce field mapping labels were being overwritten by auto-labeling.
    • Added filter gf_salesforce_autolabel to turn off auto-labeling by adding add_filter('gf_salesforce_autolabel', '__return_false'); to your theme’s functions.php file.
    • Made auto-labeling much less aggressive: now only matches exact matches for First Name, Company, etc.
  • Added support for checkboxes and other multiple-item fields using implode() PHP functionality: lists will be converted to comma-separated values.

1.1.1

  • Fixes issue where all forms get submitted to Salesforce, not only enabled forms (reported on support forum).
  • Added a new filter to modify the lead source gf_salesforce_lead_source, as requested here. Passes three arguments: $lead_source, $gf_form_meta, $salesforce_data.

1.1

  • Added support for Custom Fields (view the FAQ here, or the Gravity Forms Salesforce Add-on Settings page for this plugin)
  • Improved authentication check in the settings page – no longer creates a blank lead.
  • Fixed some PHP notices

1.0

  • Launch!