FormCourier CRM Pro Documentation

Release: 1.3.0

FormCourier CRM Pro sends submissions from supported WordPress form plugins to eight CRM platforms, with visual field mapping, a retry queue, privacy-aware tracking, Telegram notifications, logs and diagnostics.

6 form plugins 8 CRM integrations PHP 7.4+ WordPress 6.2+ Translation ready

1. Requirements and compatibility

ComponentRequirement
WordPress6.2 or newer. Tested up to WordPress 7.1.
PHP7.4 or newer. PHP OpenSSL is required for encrypted credentials and background queue modes.
PermissionsWordPress administrator access.
FormsAt least one supported form plugin must be installed and active.
CRMAn account and API credentials for the selected CRM provider.
HTTPSRecommended for production sites and external API communication.

Supported form plugins

  • Contact Form 7
  • WPForms
  • Fluent Forms
  • Forminator
  • Ninja Forms
  • Gravity Forms

Supported CRM systems

  • HubSpot CRM
  • Bitrix24
  • KeepinCRM
  • Zoho CRM
  • SalesDrive
  • Pipedrive
  • NetHunt
  • KeyCRM

2. Installation

  1. Open Plugins → Add New → Upload Plugin in WordPress.
  2. Select the installable file formcourier-crm-pro-1.3.0.zip.
  3. Click Install Now, then Activate Plugin.
  4. Open FormCourier CRM Pro → Settings.
  5. Review FormCourier CRM Pro → System Status before configuring production credentials.
WPBay package: do not upload the outer WPBay marketplace package directly to WordPress. First extract the package on your computer, open the Plugin folder, and upload formcourier-crm-pro-1.3.0.zip.

3. Quick start

  1. In the General tab, enable the integration and select one form provider and one CRM provider.
  2. Open the CRM tab, enter the provider credentials and run the available connection test.
  3. Open Forms & Mapping and map each technical form field to the matching CRM field.
  4. Choose Send immediately for the first test. Move to background queue mode after confirming OpenSSL and cron operation.
  5. Submit a real test form.
  6. Check Logs and the destination CRM record.
  7. Enable Telegram, UTM tracking or queue processing only after the basic CRM path is working.
Start with one form, one CRM entity and only the required fields. Add custom fields after the first successful submission.

4. Forms and field mapping

The Form field column uses the technical identifier produced by the selected form plugin, not always the visible label.

ProviderForm field valueExample
Contact Form 7Shortcode field name[email your-email]your-email
WPFormsNumeric field IDwpforms[fields][2]2
Fluent FormsInput nameemail
ForminatorInput nameemail-1
Ninja FormsNumeric field ID6
Gravity FormsField ID or input ID3 or 1.6

Automatic service fields

form_id
form_name
utm_source
utm_medium
utm_campaign
utm_term
utm_content
landing_page
referrer

Default mappings apply to all forms of the selected provider. Form-specific mappings override the default mapping for one real form ID.

The settings screen blocks incomplete rows, duplicate form fields, duplicate CRM targets and duplicate form IDs before saving. Server-side validation repeats these checks.

5. Sending modes and retry queue

ModeUse case
Send immediatelyBest for initial configuration and sites without a reliable cron setup.
Background queueStores encrypted submissions and processes them asynchronously with retry attempts.
Queue onlyStores submissions for controlled/manual processing.

Queue modes require PHP OpenSSL. If encryption is unavailable, FormCourier CRM Pro safely falls back to immediate sending and does not save new secrets in plaintext.

Queue administration

  • Retry one item or selected failed/dead items.
  • Restart dead items with a new attempt cycle.
  • Delete selected dead items.
  • Delete sent items older than the configured retention period.
  • Review request, response and attempt history without exposing saved credentials.
When WP-Cron is disabled, configure a real server cron job that calls wp-cron.php. Otherwise background items remain pending.

6. UTM tracking and privacy

Four tracking modes are available:

  1. Do not track - no attribution values are collected and existing FormCourier CRM Pro tracking cookies are removed.
  2. Current page only - reads values from the current page without persistent cookies.
  3. Store after consent - stores attribution only after a supported consent system grants permission.
  4. Always store - stores first-party attribution cookies without waiting for a consent integration; the site owner is responsible for legal configuration.

Supported consent integrations include Complianz, CookieYes, Cookiebot and the WP Consent API. Advertising identifiers such as gclid and fbclid are disabled by default.

Suggested privacy-policy text is available in Settings → Privacy → Policy Guide. The site owner remains responsible for adapting it to the actual forms, CRM provider, Telegram use and retention settings.

7. Telegram notifications

  1. Create a bot and copy its token.
  2. Obtain the target chat ID.
  3. Open the Telegram settings tab.
  4. Save the token and chat ID, select the send timing and test the connection.
  5. Customize the message template with supported placeholders.

Empty label-only lines are removed after placeholder replacement. Telegram failures are logged separately and do not turn a successful CRM delivery into a failed CRM result.

8. Logs, diagnostics and data management

Logs

Filter records by status, action and masked email. Detailed payload logging is optional and should be enabled only while troubleshooting.

System Status

The diagnostic page checks plugin and PHP versions, OpenSSL, HTTPS, WP-Cron, database versions, provider routing, tracking consent, privacy settings, Telegram configuration and queue health.

The downloadable JSON report excludes credentials, API tokens, webhook URLs, personal data, submission payloads and CRM request/response bodies.

Import and export

Exports contain non-secret settings and mappings. Existing secrets remain stored locally and are not included in exported JSON. Imports accept only validated FormCourier CRM Pro JSON files up to 1 MB.

9. License and updates

WPBay purchases: no additional FormCourier CRM Pro license-key activation is required. All plugin features are available after installation.

Updating a WPBay purchase

  1. Sign in to your WPBay account and download the latest FormCourier CRM Pro package from your purchased products.
  2. Extract the downloaded WPBay package on your computer.
  3. Open the Plugin folder and locate the latest installable ZIP, for example formcourier-crm-pro-1.3.0.zip.
  4. Before updating, create a backup of your WordPress site.
  5. In WordPress, open Plugins → Add New → Upload Plugin and upload the new ZIP file.
  6. If WordPress detects the existing version, choose Replace current with uploaded.
  7. After the update, verify the plugin version and submit a test form.

WPBay customers receive updates and support according to the license purchased through the WPBay marketplace.

The same plugin contains a dormant foundation for future direct licenses and checksum-verified updates. Direct-license controls appear only when the site owner intentionally configures a supported HTTPS license endpoint.

10. Troubleshooting

ProblemRecommended checks
No CRM record is createdConfirm integration is enabled, credentials are correct, entity type is selected, required CRM fields are mapped and the provider connection test succeeds.
Queue items remain pendingCheck WP-Cron or server cron, OpenSSL, queue mode, next-attempt time and System Status warnings.
CRM reports a required-field errorMap the required field, confirm the form identifier and verify that the submitted value is not empty.
Duplicate mapping is highlightedUse each form field and CRM target only once inside the same mapping set.
Telegram times outCheck outbound HTTPS access to Telegram, DNS, firewall rules, proxy settings and hosting restrictions. CRM delivery may still be successful.
Credentials cannot be savedEnable the PHP OpenSSL extension. The plugin intentionally refuses to store new secrets without encryption.
UTM data is absentReview the selected tracking mode, consent state, cookie restrictions and mapping of UTM service fields.

When requesting support, include the plugin version, WordPress/PHP versions, selected form/CRM providers, exact error message and the secret-free diagnostic JSON. Never send API keys, tokens or full customer payloads.

11. Support scope

Product support covers reproducible defects in FormCourier CRM Pro, clarification of documented settings and compatibility issues with the listed integrations.

Support does not include WordPress installation, server administration, configuration of third-party CRM accounts, creation of custom CRM schemas, custom development, data migration or troubleshooting unrelated third-party plugins.

Before opening a support request, update to the latest marketplace version, reproduce the issue with a minimal mapping and attach the secret-free diagnostic report.