Zoho CRM European Hosted Accounts

Zoho CRM European Hosted Accounts

Sample IssuesIssue Sample 1Issue Sample 2

As of Zoho CRM version 1.7, it is no longer necessary to use the filters below if your account is hosted in the EU.

Only follow the directions below if you are using a version previous to Zoho CRM Add-On 1.7. It is highly recommended that the latest version of Zoho CRM is downloaded, because along with the changes to handle accounts hosted in the EU, the update uses Zoho CRM’s new API Version 2.0. API Version 1.0 is deprecated and its end-of-life date is 12/31/2019.

If your Zoho CRM account is hosted in the EU you will need to configure the add-on to use different endpoints by adding some code snippets to your theme functions.php file or a custom functionality plugin.
1234567add_filter( ‘gform_zoho_accounts_api_url’, function() {return ‘https://accounts.zoho.eu’;} ); add_filter( ‘gform_zoho_api_url’, function() {return ‘https://crm.zoho.eu/crm/private/’;} );
Sample Issues
Issue Sample 1
Hi, I am trying to Authenticate the Zoho CRM addon and using my Zoho login details. Everytime I save my email and password, it says “the user does not exist.” Even when I try to use the Authentication token option, it has a red ‘x’ next to the field and doesn’t register the token. This is not allowing me to create a feed and keeps bringing me back to the settings.
Issue Sample 2
I’m experiencing some trouble with setting up the Zoho CRM add-on. I’ve downloaded and activated the add-on one site within a multisite. When I enter the credentials for Zoho I get an error that the user doesn’t exist. I’m certain the user does exist in Zoho, because I’m able to login to Zoho with this user. I’ve enabled debugging and debugged the code locally, but I keep getting this response. I’ve updated the Gravity Forms plugin in the local environment, but this didn’t help.

上次修改 2021.12.28

Zoho CRM Potential Data Errors

Zoho CRM Potential Data Errors

SummaryError NotesData FormatData SizeContact/Lead Already Exists

Summary
When data is sent to Zoho CRM for processing, errors may occur. Some errors are related to the data format or size. If an error does occur, the error message will be saved into a note on the entry. Data format or size errors do not prevent the contact/lead from being created in Zoho CRM. The bad data is simply not saved with the contact/lead. A few errors that may occur are listed below.
Error Notes
Data Format
If the data sent is in the wrong format, such as including the @ with the Twitter handle, a message similar to below will be saved as an entry note.

Data Size
Some fields have set field sizes, and if the data sent exceeds the limit, a message like below is sent. To prevent this issue, a Maximum Characters size limit may be set for the field in the Form Editor.

Contact/Lead Already Exists
When creating a feed, there is the setting Update Contact/Lead if contact/lead already exists for email address. If this setting is not checked, the contact/lead is not updated and a message like below is added as a note on the entry.

上次修改 2021.12.28

Zoho CRM Feed Meta

Zoho CRM Feed Meta

IntroductionUsagePropertiesContact PropertiesLead PropertiesTask PropertiesCustom Field Properties

Introduction
The Feed Object meta for the Zoho CRM add-on is an associative array containing the properties which determine how the add-on should process the form submission.
12345678$feed[‘meta’] = array(    ‘feedName’                                => ‘Zoho CRM Feed 1’,    ‘message’                                 => ”,    ‘feed_condition_conditional_logic’        => true,    ‘feed_condition_conditional_logic_object’ => array(        ‘conditionalLogic’ => array(),    ),);
Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
1$conditional_logic_enabled = rgars( $feed, ‘meta/feed_condition_conditional_logic’ );

Properties

feedName string
The feed name which appears on the add-ons feeds tab.

action string
The action which will occur when this feed is processed. Possible values: contact or lead.

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

Contact Properties
The following properties are only applicable when the action is set to contact.

contactStandardFields_Email string
The ID of the form field containing the contact’s email.

contactStandardFields_First_Name string
The ID of the form field containing the contact’s first name.

contactStandardFields_Last_Name string
The ID of the form field containing the contact’s last name.

contactCustomFields array
A multidimensional array containing the contact custom fields. See Custom Field Properties.

contactOwner string
The Zoho CRM user ID to be assigned to this contact.

contactLeadSource string
The source from which the contact is created. Default values: Advertisement, Cold Call, Employee Referral, External Referral, OnlineStore, Partner, Public Relations, Sales Mail Alias, Seminar Partner, Seminar-Internal, Trade Show, Web Download, Web Research, and Chat.

contactDescription string
The contact description. Merge tags supported.

contactAttachments array
1234array(    ’10’ => true,    ’11’ => false,);
An array of file upload fields. The field ID is the key with a boolean value indicating if the files for that field should be attached.

contactApprovalMode boolean
Is approval mode enabled? Default is false.

contactWorkflowMode boolean
Should workflow rules be triggered when this contact is added? Default is false.

contactEmailOptOut boolean
Remove contact from your mailing list so that they will not receive any emails from your Zoho CRM account. Default is false.

contactUpdate boolean
Update contact if existing? Default is false.

Lead Properties
The following properties are only applicable when the action is set to lead.

leadStandardFields_Company string
The ID of the form field containing the lead’s company.

leadStandardFields_Email string
The ID of the form field containing the lead’s email.

leadStandardFields_First_Name string
The ID of the form field containing the lead’s first name.

leadStandardFields_Last_Name string
The ID of the form field containing the lead’s last name.

leadCustomFields array
A multidimensional array containing the lead custom fields. See Custom Field Properties.

leadOwner string
The Zoho CRM user ID to be assigned to this lead.

leadRating string
The lead rating. Default values: Acquired, Active, Market Failed, Project Cancelled, and ShutDown.

leadSource string
The source from which the lead is generated. Default values: Advertisement, Cold Call, Employee Referral, External Referral, OnlineStore, Partner, Public Relations, Sales Mail Alias, Seminar Partner, Seminar-Internal, Trade Show, Web Download, Web Research, and Chat.

leadStatus string
The lead status. Default values: Attempted to Contact, Contact in Future, Contacted, Junk Lead, Lost Lead, Not Contacted, and Pre Qualified.

leadDescription string
The lead description. Merge tags supported.

leadAttachments array
1234array(    ’10’ => true,    ’11’ => false,);
An array of file upload fields. The field ID is the key with a boolean value indicating if the files for that field should be attached.

leadApprovalMode boolean
Is approval mode enabled? Default is false.

leadWorkflowMode boolean
Should workflow rules be triggered when this contact is added? Default is false.

leadEmailOptOut boolean
Remove lead from your mailing list so that they will not receive any emails from your Zoho CRM account. Default is false.

leadUpdate boolean
Update lead if existing? Default is false.

Task Properties

createTask boolean
Should a task be created? Default is false.

taskSubject string
The task subject. Merge tags supported.

taskDueDate integer
The number of days until the task is due.

taskOwner string
The Zoho CRM user ID to be assigned to this contact.

taskStatus string
The task status. Default values: Not Started, Deferred, In Progress, Completed, and Waiting on someone else.

Custom Field Properties
1234array(    ‘key’   => ‘title’,    ‘value’ => ‘3’,)
Each custom field is an associative array containing the following properties:

key string
The field name. Possible values: the Zoho field name or gf_custom.

Zoho CRM Contacts Module Fields
Zoho CRM Leads Module Fields
Zoho CRM Tasks Module Fields

value string
The ID of the form field or entry meta item containing the value for this custom field.

custom_key string
The custom key. Only used when the custom field key is set to gf_custom.

上次修改 2021.12.28

Zoho CRM Change Log

Zoho CRM Change Log

2.0 | 2021-10-271.13 | 2021-05-051.12 | 2020-09-231.11 | 2020-07-141.101.9 | 2020-05-141.8 | 2019-08-081.7 | 2019-04-251.6 | 2019-04-151.5 | 2018-03-301.4 | 2017-01-051.3 | 2016-08-311.2 | 2016-02-101.1 | 2015-09-141.0 | 2015-07-30

2.0 | 2021-10-27

Fixed a fatal error that occurs after refreshing authentication tokens with the Zoho API.

1.13 | 2021-05-05

Added a menu icon for Gravity Forms 2.5.
Fixed an issue where the reauthentication notice appears for users who have never authenticated before.
Fixed compatibility issues with PHP 8.
Fixed an issue where authentication may not complete after attempting a connection with Zoho.

1.12 | 2020-09-23

Added support for Gravity Forms 2.5.
Fixed an issue where the add-on would attempt to use deactivated module layouts.

1.11 | 2020-07-14

Added security enhancements.
Fixed an infinite loop which occurred when the record insert error returned by Zoho CRM is missing the api_name.

1.10

Added security enhancements.

1.9 | 2020-05-14

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for the Australia (AU) data center.
Added license key to authorization url.
Added the gform_zohocrm_record filter to modify the record arguments before they are sent to Zoho CRM.
Fixed the width of the Feed Name setting on the feed configuration page.
Fixed an issue where PHP notices thrown after gform_zohocrm_record introduced.
Fixed an issue where PHP notices thrown when the contact or lead has no Email but doesn’t allow duplicate in the settings.
Updated a few labels on the settings page related to connecting and disconnecting the add-on with Zoho CRM.

1.8 | 2019-08-08

Added security enhancements.
Added gform_zohocrm_post_create_lead, gform_zohocrm_post_create_contact and gform_zohocrm_post_create_task, to allow custom actions to be performed after creating a lead, contact or task.
Updated Authenticate With options. After switching to OAuth Authentication, remove the other old options.
Updated the feed configuration page to support mapping checkbox (boolean) type Zoho fields.
Fixed an issue when a Zoho account used a non-English language, some module fields couldn’t be updated with REST API.
Fixed an issue when Contacts, Leads or Tasks module is missing, REST API couldn’t work at all.
Fixed an issue where Blueprints weren’t triggered when adding Contacts/Leads in Workflow Mode with v2 API.
Fixed an issue where fields (especially Last Name and Email fields) missing from the feed settings for non-English Zoho accounts users.
Fixed an issue where values mapped to checkbox type Zoho fields would not be passed to the API.
Fixed the “Field cannot be found at Zoho CRM” issue with v2 API.

1.7 | 2019-04-25

Added support for multiple data center when authenticating with v2 API.

1.6 | 2019-04-15

Added supports for Zoho CRM v2 REST API.
Added supports for Approval Process if “Approval Mode” is checked in feed settings, when authenticated with REST API.
Fixed feed settings not saving when selecting a choice containing an ampersand.
Fixed the setting for delaying feed processing until after payment not being added to the PayPal Standard feed configuration page.
Fixed issue when using special characters to create contacts.

1.5 | 2018-03-30

Added security enhancements.
Added logging statements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Updated module field map to allow for custom fields to be used.
Updated strings for translations.
Fixed a PHP fatal error which can occur on the feeds page if the Zoho account user does not have permission to access the contacts or leads modules.
Fixed the settings page not showing an error when the maximum number of allowed auth tokens has been exceeded.
Fixed an issue with the response code logging statement.
Fixed an issue with a few strings using the wrong text domain for translations.
Fixed an issue which prevented files being sent to Zoho.
Fixed owner not being set on the created contact/lead.
Fixed an issue retrieving the ID of the created contact from the API response which also caused contact task creation to fail.

1.4 | 2017-01-05

Updated contact, lead and task creation error reporting.
Fixed module fields not importing in certain scenarios.
Fixed strings for translations.

1.3 | 2016-08-31

Added hook to allow API URL to be changed.
Updated not to force standard fields to be required. The required state of the field on the feed will match the required state of the field in the Zoho account.
Fixed issue where checking for duplicate leads did not correctly update duplicate leads.
Fixed an issue where Zoho was unable to parse the XML data if the value contained special characters.
Fixed an issue with the request failed message if a WP_Error occurs.

1.2 | 2016-02-10

Added support for configuring a task description.
Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Added some additional logging.
Updated the task due date setting to support merge tags. The merge tag value must be numeric for the due date to be set.
Updated to display an error for the password field on the settings page if Zoho returns a WEB_LOGIN_REQUIRED error.
Fixed an issue with the request failed message if a WP_Error occurs.
Fixed an issue with the text domain for some of the translatable strings.
Fixed an issue with how multiple choices in multi select and checkbox type field values are separated when being sent to Zoho.
Fixed module field choices return “Array” as an option.
Fixed fatal error that occurs during 1.1.5 upgrade routine.
Fixed contacts and leads not being created when Zoho CRM account language is not set to English.
Fixed module field loading to support foreign languages.

1.1 | 2015-09-14

Added authentication option for third party services (Google Apps, Facebook, Yahoo).
Added options to allow for duplicate contacts and feeds.
Added option to manually clear custom fields cache.
Changed custom fields cache from 24 hours to 12 hours.
Fixed an issue where only some of the uploaded files were attached.
Updated available field types for mapping to the contact/lead email.

1.0 | 2015-07-30

It’s all new!

上次修改 2021.12.28

Zapier Feed Meta

Zapier Feed Meta

IntroductionUsageProperties

Introduction
The Feed Object meta for the Zapier add-on is an associative array containing the properties which determine how the add-on should process the form submission.
$feed[‘meta’] = array(
‘feedName’ => ‘Your Feed Name’,
‘feed_condition_conditional_logic’ => true,
‘feed_condition_conditional_logic_object’ => array(
‘conditionalLogic’ => array(),
),
);

Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
$conditional_logic_enabled = rgars( $feed, ‘meta/feed_condition_conditional_logic’ );

Properties

feedName string
The feed name which appears on the add-ons feeds tab.

zapURL string
The Zapier hosted URL where the entry data will be sent when the feed is processed.

adminLabels string
Indicates if the field admin labels should be sent to Zapier instead of the main labels, if configured. Possible values: 1 or 0.

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

legacy boolean
Indicates if the feed was migrated from the non-framework version of the add-on (pre 4.0).

legacy_id int
The feed ID when it was stored in the legacy rg_zapier table.

上次修改 2021.12.28

Zapier Change Log

Zapier Change Log

4.1.14.1 | 2021-05-044.0 | 2021-02-233.3 | 2020-05-203.2 | 2019-09-253.1 | 2018-10-223.0 | 2018-05-072.1.7 | 2018-03-202.1.6 | 2018-03-162.1.5 | 2018-01-312.1.4 | 2017-10-022.1.3 | 2017-05-092.1.2 | 2017-04-262.1.1 | 2017-03-122.1 | 2017-01-052.0 | 2016-08-311.9 | 2016-07-011.8 | 2015-08-181.7 | 2015-04-201.6 | 2015-03-301.4 | 2014-02-031.1 | 2013-08-14

4.1.1

Updated the gform_zapier_request_body filter to be called within GF_Zapier::get_body so that it can be applied both when processing feeds and responding to API requests.

4.1 | 2021-05-04

Added support for displaying real entry data for the selected form when configuring a Zap.
Added support for using admin labels instead of front end labels for the entry data returned when configuring a Zap.
Fixed an issue where API instructions are not visible on the add-on settings page when using Gravity Forms 2.5.
Fixed an issue where feeds get deleted and recreated when the Zap is deactivated and reactivated.
Updated the Use Admin Labels setting on the feed configuration page to be disabled. The setting is now configured on zapier.com.
Removed the add new button from the feeds list page.

4.0 | 2021-02-23

Added support for the Gravity Forms Integration App on Zapier v2.0.
Added an add-on setting to toggle the display of Zapier Feeds in the form settings. On sites with legacy feeds created for the Zapier v1.0 integration, this setting is enabled by default, displaying all the feeds. On sites with no legacy feeds, this setting is off by default so the feeds will not be displayed.
Fixed compatibility issues in PHP 8.
Updated the feed settings to restrict editing of feeds created in the Zapier v2.0 integration to Admin Labels and Conditional Logic.
Updated the add-on to use the Gravity Forms Add-On Framework.

3.3 | 2020-05-20

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fixed an issue where the entry and payment dates were being formatted before being sent to Zapier.

3.2 | 2019-09-25

Added support for triggering Zapier feeds after a successful delayed payment (we originally did it only for PayPal). This fixed an issue where feeds are triggered before payments received when using Stripe Checkout.
Added gform_zapier_request_body filter to allow the request body sent to Zapier to be modified.
Fixed notice in gform_zapier_use_stored_body filter processing.
Fixed the shipping line item being included in the request body when the shipping field is hidden by conditional logic.
Fixed PHP 7.3 warnings when the feed is populating the request body for a form with multiple product fields.

3.1 | 2018-10-22

Added the gform_zapier_products filter.
Updated data sent to Zapier to include extra entry properties and the form ID.
Fixed missing product fields.

3.0 | 2018-05-07

Added line item support for list field and product fields.

2.1.7 | 2018-03-20

Fixed issue when trying to get random choices on an empty array.

2.1.6 | 2018-03-16

Fixed an issue where feeds could, in some situations, be processed following PayPal payment when not selected as delayed on the PayPal feed.

2.1.5 | 2018-01-31

Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.

2.1.4 | 2017-10-02

Fixed feeds not running when the form is embedded in an admin page or a front-end page via an Ajax request.

2.1.3 | 2017-05-09

Added security enhacements.
Fixed code styles.

2.1.2 | 2017-04-26

Added support for the Gravity Forms 2.2+ System Status page.

2.1.1 | 2017-03-12

Added the gform_zapier_use_stored_body filter.

2.1 | 2017-01-05

Added support for the gform_is_delayed_pre_process_feed filter.
Updated strings for translations.
Updated Zapier Feeds table to be responsive.
Fixed issue where Zapier did not appear alphabetical in the Settings list.

2.0 | 2016-08-31

Added the gform_zapier_sample_field_value filter for overriding the sample data sent when configuring the zap or updating the form.
Updated to format entry date.
Fixed an issue with the ‘Use Admin Labels’ setting on new zaps appearing to reset when saving a valid zap.
Fixed PHP warning which could occur if the multiselect field only had one choice configured.

1.9 | 2016-07-01

Added support for sending the field admin label to Zapier, if available.
Added GFZapier::process_feed( $feed, $entry, $form ) for processing a single feed.
Updated to send the form title, entry id, entry date, user ip and source url.
Updated minimum Gravity Forms version to 1.9.10.
Updated to send dummy values to Zapier when saving the feed/form instead of empty values.
Updated to skip display only fields when preparing the zap body array.
Updated to use the field title when preparing the zap body if the field doesn’t have a label.
Updated minimum Gravity Forms version to 1.9.
Updated to support Gravity Forms 2.0 changes to the PayPal Standard integration.
Fixed an issue where field values in the body array would be overridden if another field used the same label.
Fixed PHP notices on the edit feed page related to the conditional logic field and value settings.
Fixed an issue with the feed conditional logic value drop down for choice based fields.
Fixed GF_Field array access/object notation notice with Gravity Forms 2.0.
Fixed an issue with the PayPal Standard integration.

1.8 | 2015-08-18

Added the gform_zapier_feed_conditional_logic filter enabling the feed conditional logic rule to be overridden during submission, allowing multiple rules to be defined.

1.7 | 2015-04-20

Added text domain/path to header.
Fixed an issue with multi-input fields and the dummy data sent to Zapier when first configuring a zap or updating the form.
Fixed a low severity security vulnerability in the admin area which could be exploited by authenticated users with form administration permissions.
Fixed an issue with conditional logic evaluation when processing feeds delayed by the PayPal Standard add-on.

1.6 | 2015-03-30

Added Spanish (es_ES) translation.
Added ability to delay sending to Zapier until a payment is received if PayPal Standard is also being used.
Updated POT file.
Updated to not send entries marked as spam to Zapier.
Fixed an issue with the zap body being prepared even if the form does not have a feed.
Fixed a warning for multi-row Likert fields when the zap body is being prepared.
Fixed a warning related to how Gravity Forms 1.9 handles inputs for fields such Email, Date and Time.
Fixed notice thrown when using extract in certain PHP versions.
Fixed the functions used by the mwp_premium_update_notification and mwp_premium_perform_update hooks so that the new_version element in the array returns Zapier’s version instead of Gravity Forms.
Fixed strict notice thrown when viewing the list of Zaps for a form.

1.4 | 2014-02-03

Added POT file.
Added entry meta to field list.
Added the gform_zapier_field_value hook so the value can be modified before sending to Zapier.
Fixed issue where the anti-spam honeypot being active was causing data to not be passed to Zapier.
Fixed notices.

1.1 | 2013-08-14

Updated how multi-input fields (checkboxes, name, address) are handled so that users can map to the “parent” field (in addition to being able to map to the individual inputs).

上次修改 2021.12.28

Using the Zapier Add-On

Using the Zapier Add-On

IntroductionPre-RequisitesQuick Getting StartedSetting up the Zapier Add-OnZapier Actions and TriggersZapsZapier HelpWhat Can You Do with Zapier and Gravity Forms?

Introduction
The Gravity Forms Zapier Add-On allows you to integrate Gravity Forms with over 200+ (and counting) online services. Zapier enables you to automate tasks between other online services such as Salesforce, Basecamp, GMail, and over 200 more.
Capture data via a Gravity Form that automatically creates a lead in Salesforce, a new row in a Google Spreadsheet, and a new calendar event in Google Calendar. All from the same single form submission.
The Gravity Forms Zapier Add-On does not replace our existing add-ons such as MailChimp, Campaign Monitor, etc. but does provide you with a way to integrate with services that we may not already support via official Add-Ons. Just as we consider Gravity Forms a swiss army knife for WordPress, Zapier is a swiss army knife for Gravity Forms.
In order to use the Gravity Forms Zapier Add-On you must have a Zapier account. Zapier is a paid service and pricing is based on volume and usage. You can find more about Zapier pricing here.
Unlike most Gravity Forms Add-Ons, the majority of the setup involved in integrating with Zapier will occur on the Zapier side via their customer dashboard. This does mean if you are having an issue with a Zap you have created in Zapier not behaving the way you expected, you may need to contact Zapier support for assistance for issues that occur within their Zapier Dashboard, Zap setup, and behavior.
Pre-Requisites

Download and install the add-on
A Zapier account
Signing up can be done quickly and easily and includes a 14-day free trial which gives you access to every regular and premium app. After the free trial, you can continue to use the free plan or select one of the available premium plans.
SSL Certificate Installed and Configured
Website Accessible to the Internet. The new authentication from Zapier to Gravity Forms uses REST API so your website must be accessible to Zapier.

Quick Getting Started

Create a Zapier REST API Connection under Forms, Settings, REST API. Save the Consumer Key and Consumer Secret for step 2.
Create a Zapier App Connection to Gravity Forms in MyApps. You will use the Consumer Key and Consumer Secret from step 1
Create a Gravity Form to send information to Zapier.
Create a Zap under your Zapier account to connect to the form you created. You’ll use the Gravity Forms connection created in Step 2.

Setting up the Zapier Add-On
Use this reference to configure your Zapier Application Connection to Gravity Forms
Zapier Actions and Triggers
You can use your Gravity Forms as both a Zapier trigger and as a Zapier action.
In both cases, the set-up process is done completely from within your Zapier account.
Zaps
To start sending data between Zapier and your forms, create a Zap as normal from within your Zapier account. You’ll be using the Gravity Forms connection.

Zapier Help
Most of your configuration with Gravity Forms and Zapier will take place within your Zapier account. If you run into issues, and you’ve confirmed that Zapier is communicating with the REST API connection in Gravity Forms, you can reach out to Zapier for assistance. You can check out their help documentation here.
What Can You Do with Zapier and Gravity Forms?
Zapier has 2000+ of Web Applications that can potentially integrate with Gravity Forms. Check out some of the most popular Zaps that you can use to work with Gravity Forms and these applications.

Create rows in Google Sheets for new Gravity Forms submissions
Use this Zap
Add contacts to Hubspot from new Gravity Forms entries
Use this Zap
Create HubSpot contacts from new Gravity Forms submissions
Use this Zap
Create Salesforce leads with new Gravity Forms submissions
Use this Zap
Create Google Calendar events from new Gravity Forms submission
Use this Zap

See more

Gravity Forms

integrations

powered by Zapier

上次修改 2021.12.28

Zapier Add-On Related Articles and Tutorials

Zapier Add-On Related Articles and Tutorials

SummaryGravityForms.comZapier.comOther Sites

Summary
This document contains a quick reference list of articles and tutorials from websites external to our documentation site which may help you get the most out of the Gravity Forms Zapier Add-On.
Make sure you peruse the Zapier section of our documentation site also.
GravityForms.com

What is possible with Gravity Forms and Zapier?
Supercharge your WordPress Forms with 1,000+ Apps and Services
Sending Form Entries to Google Sheets
Updating Spreadsheets from Form Entries in WordPress
Sending Form Entries to Google Calendar
Uploading Files to Google Drive from WordPress
Sending Product Information to Google Sheets using Zapier
Sending List Field and Product Data As Arrays to Zapier

Zapier.com

Gravity Forms Integrations
Gravity Forms Integration Help & Support

Other Sites

Zapier – Creating Pipedrive Deals via Gravity Forms
Send Gravity Forms Submissions to GoToWebinar
Automatically Create Base CRM Leads from Gravity Forms
Sending New Emails via SendGrid for New Gravity Forms Submissions
Asking for signatures from HelloSign for new Gravity Forms submissions

上次修改 2021.12.28

WP Config Options

WP Config Options

General OptionsGF_THEME_IMPORT_FILEGF_LICENSE_KEYMulti-Site Specific OptionsGF_RECAPTCHA_PRIVATE_KEYGF_RECAPTCHA_PUBLIC_KEYGF_IMPORT_FILECreating a Form Import JSON File

General Options
The following options are available for general use.
GF_THEME_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a theme containing this option is activated. This option should be specified in your theme’s functions.php file. Follow these steps to create a Form JSON file for use with this option.
1define( ‘GF_THEME_IMPORT_FILE’, ‘path/to/gf_import.json’ );
Note: The path is relative to your theme root.
GF_LICENSE_KEY
Setting this option before installing Gravity Forms on a single site WP installation or before creating new sites on a multisite install will automatically pre-populate your Gravity Forms license key for those new installations.
1define( ‘GF_LICENSE_KEY’, ‘YOUR-LICENSE-KEY-HERE’ );
Multi-Site Specific Options
The following options are available when using WordPress Multi-Site. All of the options below should be defined in your wp-config.php.
GF_RECAPTCHA_PRIVATE_KEY
GF_RECAPTCHA_PUBLIC_KEY
Setting these options will automatically pre-populate your ReCAPTCHA public and private keys when a new site is created on your Multi-Site install.
12define( ‘GF_RECAPTCHA_PUBLIC_KEY’, ‘YOUR-KEY-HERE’ );define( ‘GF_RECAPTCHA_PRIVATE_KEY’, ‘YOUR-KEY-HERE’ );
GF_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a new site is created on your Multi-Site install. Follow these steps to create a Form JSON file for use with this option.
1define( ‘GF_IMPORT_FILE’, ‘http://www.domain.com/path/to/gf_import.json’ );
Creating a Form Import JSON File
The following steps explain how to create a Form JSON file from which a set of default forms can be pre-generated when used with the GF_IMPORT_FILE or GF_THEME_IMPORT_FILE option.

Create the initial set of forms you want to replicate.
Navigate to the Import/Export tool and select “Export Forms”.
Select the forms you want to auto-replicate when a new site is created.
Click “Export” to export them to an JSON file.
Place the JSON file somewhere on your web server, such as your wp-content/uploads/ folder, or somewhere easily accessible.
Replace the URL in the example code above with the URL to your Form JSON file.

上次修改 2021.12.28

WP-CLI Tools

WP-CLI Tools

Clearing TransientsExamplesEmptying TrashExamplesParametersVerifying ChecksumsExamplesParametersGetting the System ReportExamplesRunning the database setup

This article includes a few extra commands which are available with the CLI Add-On for Gravity Forms.
Clearing Transients
wp gf tool clear_transients
wp gf tool clear-transients
Clears the Gravity Forms transients.
Examples
123# Successful clearing of the transients.$ wp gf tool clear-transientsSuccess: Gravity Forms transients cleared successfully.
123# Failed clearing of the transients.$ wp gf tool clear_transientsError: There was a problem clearing the Gravity Forms transients.
Emptying Trash
wp gf tool empty_trash
wp gf tool empty-trash
Delete the trashed entries.
Examples
123# Successful deletion of trashed entries for all forms.$ wp gf tool empty-trashSuccess: Trash emptied successfully for all forms.
123# Successful deletion of trashed entries for a specific form.$ wp gf tool empty-trash 2Success: Trash emptied successfully for form ID 2
Parameters

Argument
Description

[]
The ID of the form to delete the entries from. Default: all forms.

Verifying Checksums
wp gf tool verify_checksums
wp gf tool verify-checksums
Verify the Gravity Forms plugin files against the checksums.
Examples
123# Successful verification of the plugin checksums.$ wp gf tool verify-checksumsSuccess: Gravity Forms install verifies against checksums.
1234# Failed checksum verification.$ wp gf tool verify-checksumsWarning: File doesn’t exist: css/admin.min.cssError: Gravity Forms install doesn’t verify against checksums.
Parameters

Argument
Description

[–version=]
The version number the checksums should be validated against.

Getting the System Report
wp gf tool system_report
wp gf tool system-report
wp gf tool status
Outputs the system report from the Forms > System Status page.
Examples
12345# Successfully using the “system-report” command to output the system report.$ wp gf tool system-reportSuccess:### Gravity Forms ###…
123# Using the “status” alias with an older Gravity Forms version.$ wp gf tool statusError: The system report is only available with Gravity Forms 2.2 or greater.
Running the database setup
See the Managing Gravity Forms and Add-Ons with WP-CLI article.

上次修改 2021.12.28