FormCourier CRM
FormCourier CRM

FormCourier CRM

0/5 (0 ratings) — active installs Updated Sep 19, 2026
Configure the active WordPress form provider, CRM provider, and integration settings.

Configure the active WordPress form provider, CRM provider, and integration settings.

FormCourier CRM connects Contact Form 7 and WPForms to HubSpot CRM and Pipedrive.

Map WordPress form fields to CRM fields, test your CRM connection, and send new submissions directly from your WordPress site to the CRM selected by the site administrator.

The plugin is designed for contact forms, lead capture forms, appointment forms, and other forms that need to create or update CRM records without custom integration code.

Supported integrations

FormCourier CRM supports these WordPress form and CRM combinations:

  • Contact Form 7 to HubSpot.
  • WPForms to HubSpot.
  • Contact Form 7 to Pipedrive.
  • WPForms to Pipedrive.

Each supported form provider and CRM pair has its own global field mapping.

HubSpot integration

FormCourier CRM can send mapped form submissions to HubSpot in two modes:

  • Contact only – create or update a HubSpot contact.
  • Contact + Deal – create or update the contact and create an associated deal.

Only the form values mapped by the site administrator are sent to HubSpot.

Pipedrive integration

FormCourier CRM can send mapped form submissions to Pipedrive and work with people, organizations, deals, leads, and notes according to the selected entity mode and field mapping.

Only the mapped form values and CRM identifiers required for the selected operation are sent to Pipedrive.

Main features

  • Contact Form 7 and WPForms support.
  • HubSpot contact-only and Contact + Deal modes.
  • Pipedrive person with deal or lead modes.
  • Separate global field mapping for every supported form and CRM pair.
  • Immediate delivery during form submission.
  • Built-in HubSpot and Pipedrive connection testing.
  • Local technical logs with masked email addresses.
  • Optional masked request and response payloads for troubleshooting.
  • Encrypted CRM credentials when PHP OpenSSL is available.
  • Suggested Privacy Policy text in WordPress.
  • Translation-ready interface using the WordPress.org language-pack system.
  • Bundled offline documentation and field mapping examples.
  • Lite delivery hooks automatically pause while FormCourier CRM Pro is active to prevent duplicate submissions.

How delivery works

After a site administrator configures CRM credentials, maps form fields, and enables the integration, FormCourier CRM processes supported form submissions immediately.

Typical flow:

WordPress form -> FormCourier CRM -> HubSpot or Pipedrive API

Form submissions and CRM credentials are not sent to the plugin author.

Field mapping

Use the actual Contact Form 7 field names or WPForms field IDs from your form and map them to the CRM fields you want to populate.

Mappings are global for each supported form provider and CRM pair in the Lite version.

The bundled documentation includes standard examples for name, email, phone, and message fields.

Logs and troubleshooting

FormCourier CRM includes local technical logs to help administrators verify CRM delivery results.

Logs may store the form provider, CRM provider, processing result, action, and a masked email address.

Full request and response payload logging is disabled by default. When enabled for troubleshooting, known personal and secret fields are masked before storage.

Commercial version

FormCourier CRM may show a contextual Get FormCourier CRM Pro link on the plugin settings screen and in the Plugins action links.

The link opens https://formcourier.site/, an external commercial website operated by the plugin author.

The plugin does not contact this website or send site, user, form, or telemetry data to it unless an administrator intentionally follows the link.

Privacy

FormCourier CRM does not send telemetry or usage statistics to the plugin author.

The plugin contacts a CRM only after an administrator enables the integration, selects a CRM, and saves credentials.

The fields sent depend on the administrator’s mapping and may include a visitor’s name, email address, phone number, message, form ID, and form name.

A local technical log may store the form provider, CRM provider, processing result, action, and a masked email address.

Full request and response payload logging is disabled by default. When enabled, known personal and secret fields are masked before storage.

External services

FormCourier CRM connects directly from the WordPress site to third-party CRM APIs only after a site administrator configures credentials and enables the integration.

The plugin author does not receive these requests or form submissions.

  • HubSpot API – Used to search for, create and update HubSpot contacts and, when Contact + Deal mode is selected, to create an associated deal. On form submission, the plugin sends only the form values that the administrator mapped to HubSpot properties. Depending on the mapping, this may include a visitor’s name, email address, phone number, message, form ID and form name. The configured HubSpot private app access token is sent in the HTTP Authorization header with each HubSpot API request. When an administrator runs the connection test, the plugin sends the access token and a synthetic @example.invalid email search value to verify API access; no visitor submission data is sent by the connection test. HubSpot Customer Terms of Service: https://legal.hubspot.com/terms-of-service HubSpot Privacy Policy: https://legal.hubspot.com/privacy-policy

  • Pipedrive API – Used to search for, create and update Pipedrive people and organizations and to create or update deals, leads and notes according to the administrator’s selected entity mode and field mapping. On form submission, the plugin sends only the mapped form values and related CRM identifiers required for the selected operation. Depending on the mapping, this may include a visitor’s name, email address, phone number, message/note, form ID and form name. The configured Pipedrive API token is sent in the x-api-token HTTP header with each Pipedrive API request. When an administrator runs the connection test, the plugin sends the API token to the configured *.pipedrive.com account domain and requests the current-user endpoint; no visitor submission data is sent by the connection test. Pipedrive Terms of Service: https://www.pipedrive.com/en/terms-of-service Pipedrive Privacy Notice: https://www.pipedrive.com/en/privacy

No CRM request is made until the administrator intentionally configures the relevant CRM credentials.

Form submission data is sent only when the integration is enabled.

HubSpot and Pipedrive are third-party services and are not affiliated with or endorsed by FormCourier CRM.