FormCourier CRM

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.

1.0.3

• Improved the WordPress.org plugin description and integration-focused FAQ.
• Clarified the supported Contact Form 7 and WPForms workflows for HubSpot and Pipedrive.
• Improved feature descriptions, field-mapping documentation, and screenshot captions.
• No runtime behavior was changed.

1.0.2

• Added official plugin and author website URLs.

1.0.1

• Added a contextual link to the separately distributed FormCourier CRM Pro commercial offering on the Plugins screen.
• Added a small Pro upgrade section to the Current Integration sidebar card.
• The external commercial site is contacted only when an administrator intentionally clicks the upgrade link.

1.0.0

• Promoted the fully validated release candidate to the first stable release without changing runtime behavior.
• Confirmed clean Plugin Check results for Plugin Repo, Security, General, Performance and Accessibility.
• Confirmed WordPress Coding Standards, PHP lint, JavaScript syntax and the complete PHPUnit suite.
• Finalized WordPress.org metadata, localized documentation and production packaging.

1.0.0-rc1

• Promoted the fully validated beta5 codebase to the first release candidate without adding new runtime features.
• Confirmed clean Plugin Check results for Plugin Repo, Security, General, Performance and Accessibility categories.
• Confirmed Contact Form 7 and WPForms delivery to HubSpot and Pipedrive, localized interfaces, privacy-aware logs and Lite/Pro coexistence.
• Corrected the historical beta4 changelog heading and finalized release-candidate metadata and documentation.

1.0.0-beta5

• Removed the discouraged load_plugin_textdomain() call while preserving bundled translations as a fallback when no WordPress.org language pack exists.
• Prepared custom log-table identifiers with the WordPress %i placeholder before direct database queries.
• Kept prepared values adjacent to get_results() and get_var() calls for Plugin Check analysis.
• Addressed the Plugin Repo warnings reported for beta4.

1.0.0-beta4

• Fixed corrupted Russian and Ukrainian interface text in compiled MO files.
• Added deterministic PO-to-MO compilation to release checks and builds.
• Added regression tests for MO UTF-8 headers and translated runtime strings.
• Preserved the completed WordPress Coding Standards fixes from beta3.

1.0.0-beta3

• Completed the remaining WordPress Coding Standards fixes after the beta2 audit.
• Confirmed clean WPCS, PHPUnit and release checks for the release-candidate code path.
• Preserved the validated CRM behavior, translations and Lite/Pro coexistence protection.

1.0.0-beta2

• Applied WordPress Coding Standards formatting across the runtime PHP files.
• Added complete file, class, property and function documentation.
• Reworked custom log-table SQL handling and documented intentional direct queries.
• Removed direct form POST access from Contact Form 7 email validation.
• Documented read-only administration GET parameters and cryptographic Base64 transport.
• Replaced short ternaries and corrected remaining i18n and parameter documentation issues.

1.0.0-beta1

• Prepared the plugin metadata and readme for WordPress.org review.
• Expanded external-service and privacy disclosures.
• Added WordPress.org-oriented static release checks and WPCS configuration.
• Limited the Pro conflict notice to relevant administration screens.
• Improved nonce input handling and admin output formatting.
• Excluded Composer vendor files from the plugin-source PHP lint count.

1.0.0-alpha4

• Completed Russian and Ukrainian translations for the plugin interface and CRM result messages.
• Added localized offline documentation and standard field mapping examples.