WordPress plugin intelligence profile

Forms: 3rd-Party Integration

Send contact form submissions from other plugins to multiple external services e.g. CRM. Configurable, custom field mapping, pre/post processing.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 5.2
Current version1.8
WordPress coverageTested up to WordPress 5.2
Minimum stackWP 3.0 · PHP —
Directory statusactive
Last directory update9 Sept 20197y ago
Active installations5K+Adoption metric — not a quality score
WordPress.org rating4.9 / 5 from 31 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Forms: 3rd-Party Integration version 1.8 as active, updated 7y ago and tested up to WordPress 5.2.

Overview

About this plugin

Send Contact Form 7, Gravity Forms, or Ninja Forms Submissions to a 3rd-party Service, like a CRM. Multiple configurable services, custom field mapping. Provides hooks and filters for pre/post processing of results.

Allows you to send separate emails, or attach additional results to existing emails. Comes with a couple examples of hooks for common CRMs (listrak, mailchimp, salesforce). Check out the FAQ section for add-on plugins that extend this functionality, like sending XML/SOAP posts, setting headers, and dynamic fields.

The plugin essentially makes a remote request (POST) to a service URL, passing along remapped form submission values.

Based on idea by Alex Hager “ How to Integrate Salesforce in Contact Form 7 “.

Original plugin, Contact Form 7: 3rdparty Integration developed with the assistance of AtlanticBT. Current plugin sponsored by Stephen P. Kane Consulting.

Please submit bugs / support requests to GitHub issue tracker in addition to the WordPress Support Forums because the Forums do not send emails.

Hooks

0

  • add_action('Forms3rdPartyIntegration_service_a#', $response, $param_ref);
  • hook for each service, indicated by the # – this is given in the ‘Hooks’ section of each service
  • provide a function which takes $response, &$results as arguments
  • allows you to perform further processing on the service response, and directly alter the processing results, provided as array('success'=>false, 'errors'=>false, 'attach'=>'', 'message' => '');
  • success = true or false – change whether the service request is treated as “correct” or not
  • errors = an array of error messages to return to the form
  • attach = text to attach to the end of the email body
  • message = the message notification shown (from CF7 ajax response) below the form
  • note that the basic “success condition” may be augmented here by post processing
  • add_action('Forms3rdPartyIntegration_service', $response, $param_ref, $sid);
  • same as previous hook, but not tied to a specific service
  • add_filter('Forms3rdPartyIntegration_service_filter_post_#,...
  • hook for each service, indicated by the # – this is given in the ‘Hooks’ section of each service
  • allows you to programmatically alter the request parameters sent to the service
  • should return updated $post array
  • add_filter('Forms3rdPartyIntegration_service_filter_post', 'YOUR_HOOK', 10, 4);
  • in addition to service-specific with suffix _a#; accepts params $post, $service, $form, $sid
  • add_filter('Forms3rdPartyIntegration_service_filter_args', 'YOUR_HOOK', 10, 3);
  • alter the args array sent to wp_remote_post
  • allows you to add headers or override the existing settings (timeout, body)
  • if you return an array containing the key response_bypass, it will skip the normal POST and instead use that value as the 3rdparty response; note that it must match the format of a regular wp_remote_post response.
  • Note: if using response_bypass you should consider including the original arguments in the callback result for debugging purposes.

-

add_action('Forms3rdPartyIntegration_remote_failure', 'mycf7_fail', 10, 5);

-

hook to modify the Form (CF7 or GF) object if service failure of any kind occurs — use like:

function mycf7_fail(&$cf7, $debug, $service, $post, $response) {

$cf7->skip_mail = true; // stop email from being sent

// hijack message to notify user

///TODO: how to modify the “mail_sent” variable so the message isn’t green? on_sent_ok hack?

$cf7->messages[‘mail_sent_ok’] = ‘Could not complete mail request:** ‘. $response[‘safe_message’];

}

-

needs some way to alter the mail_sent return variable in CF7 to better indicate an error – no way currently to access it directly.

  • add_action('Forms3rdPartyIntegration_service_settings', 'YOUR_HOOK', 10, 3)
  • accepts params $eid, $P, $entity corresponding to the index of each service entity and this plugin’s namespace, and the $entity settings array
  • allows you to add a section to each service admin settings
  • name form fields with plugin namespace to automatically save: $P[$eid][YOUR_CUSTOM_FIELD] $rarr; Forms3rdPartyIntegration[0][YOUR_CUSTOM_FIELD]
  • add_action('Forms3rdPartyIntegration_service_metabox', 'YOUR_HOOK', 10, 2)
  • accepts params $P, $entity corresponding to the index of each service entity and this plugin’s namespace, and the $options settings array (representing the full plugin settings)
  • allows you to append a metabox (or anything else) to the plugin admin settings page
  • name form fields with plugin namespace to automatically save: $P[YOUR_CUSTOM_FIELD] $rarr; Forms3rdPartyIntegration[YOUR_CUSTOM_FIELD]
  • add_filter('Forms3rdPartyIntegration_debug_message', 'YOUR_HOOK', 10, 5);
  • bypass/alternate debug logging
  • add_filter('Forms3rdPartyIntegration_plugin_hooks', 'YOUR_HOOK', 10, 1);
  • Accepts an array of contact form plugin hooks to attach F3p to, and returns that array. Modify result to attach to additional plugin hooks, like GF edit.
  • add_filter('Forms3rdPartyIntegration_service_filter_url', 'YOUR_HOOK', 10, 2);
  • hook a function that takes the $service_url, $post_args and returns the endpoint $url
  • used to modify the submission url based on mappings or other information
  • $post_args contains the body and other wp_remote_post details

Basic examples provided for service hooks directly on plugin Admin page (collapsed box “Examples of callback hooks”). Code samples for common CRMS included in the /3rd-parties plugin folder.

Stephen P. Kane Consulting

From the website and Handpicked Tomatoes:

Transparent and Holistic Approach

>

Transparency is good. It’s amazing how many web design sites hide who they are. There are lots of reasons, none of which are good for the customer.

We don’t do that. I’m Stephen Kane, principal web craftsman at HandpickedTomatoes, and I’m an Orange County based freelancer who occasionally works with other local freelancers and agencies to deliver quality web solutions at very affordable prices.

We work to earn the right to be a trusted partner. One that you can turn to for professional help in strategizing, developing, executing, and maintaining your Internet presence.

We take a holistic view. Even if a project is small, our work should integrate into the big picture. We craft web architecture and designs that become winning websites that are easy to use and to share.

, and google places and integrate them into your website to leverage social marketing. We help you set up and execute email campaigns, with search engine marketing, with photography, with site copy and content and anything else that you need in order to have a successful Internet presence.

Through this holistic approach, we work with clients to grow their sales, improve their brand recognition, and manage their online reputation.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • contact form
  • contact form 7
  • gravity forms
  • cf7
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 5.2

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 5.2.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to5.2
Minimum requirementsWordPress 3.0 · PHP not listed
Update activity9 Sept 20197y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.