Limited-Time Offer

Get Extra 20% off on FullCharge Yearly Plan — available for first 10 users only. Don’t miss out! 🚀

TrackWP

FormsCRM · Version history

FormsCRM changelog and version history

Latest version
4.4.5
Nov 4, 2026 (4 days ago)
Releases
64
since 2021
In the last year
14
about one every 27 days
Tested up to
WordPress 7.1.4

Releases each year

  • 20217 releases
  • 202212 releases
  • 20239 releases
  • 202415 releases
  • 202511 releases
  • 202610 releases

202610 releases

  1. FormsCRM 4.4.5Latest

    • Fixed: Gravity Forms entries on forms with a Clientify feed were flagged as spam by the honeypot since 4.4.4. The Clientify tracking field was added as a Gravity Forms field only when rendering the form, which shifted the honeypot field ID, so the honeypot check read the filled tracking field. It i…

  2. FormsCRM 4.4.4

    • Added: Support for Clientify’s Analytics PLUS contact attribution. FormsCRM automatically captures the pixel’s visitor_uuid from localStorage in the browser and forwards it as visitor_key on contact creation, linking the contact to the visit the Analytics PLUS pixel tracked. (Clientify’s visitor_ke…
    • Enhanced: Clientify’s legacy vk tracking cookie is now captured client-side (the cookie may be set/refreshed by the pixel after the page has already loaded, so the server-side copy isn’t reliable) and forwarded automatically as visitor_key too, as a fallback when there’s no Analytics PLUS visitor_u…
    • Changed: Every Clientify-connected form (Gravity Forms, Contact Form 7, Elementor) now gets FormsCRM’s own hidden field injected automatically to carry the tracking identifier, filled by a small script FormsCRM enqueues on demand. It’s not a mappable field — its value is dynamic per visit and can’t…
    • Fixed: Clientify merge strategy could update the wrong contact/company. Clientify’s query search param is a substring match (e.g. searching “molina@gmail.com” could match “aestepamolina@gmail.com”), and the merge strategy took the first search result without verifying it was an exact match. It now…
    • Fixed: the “Email Main” field-mapping option and the “Email Main” typed-email option showed the same label, so mapping the wrong one silently defeated the merge strategy (fell back to creating instead of updating) with no warning. The native field is now labeled “Email Main (single field)”.
    • Fixed: marketing_status defaulted to “Marketing Contact” was also sent when updating an existing contact via the merge strategy, silently overwriting a contact intentionally set as “Sales Contact”. The default is now only applied when creating a new contact.
    • Enhanced: Added support for GravityForms 3.0’s international Phone field format, normalizing the number (digits and leading “+”) before sending it to the CRM.
    • Fixed: Elementor forms connected to Clientify always forced contact creation (force_insert=true), causing an HTTP 409 Conflict on every resubmission from an existing contact. The merge strategy field (used to search and update instead of create) is now available for Elementor, same as Gravity Forms.
    • Developers: New formscrm_alert_error_labels filter to customize the wording of error alerts (email subject, headers, Slack title and labels), so addons can describe their own failure types (e.g. a payment error) instead of the generic lead creation error.
    • Tests: Pinned Contact Form 7 to 6.1.7 in the PHPUnit installer, since Contact Form 7 6.2+ requires PHP 8.3 and broke the test suite on PHP 7.4 and 8.1.

  3. FormsCRM 4.4.3

    • Fixed: Clientify API v1 requests occasionally failing with HTTP 504 Gateway Timeout on api.clientify.net. All requests (reads, lead/contact creation, updates, deals) now retry once against the api.clientify.com fallback before failing; this is a temporary workaround suggested by Clientify support w…

  4. FormsCRM 4.4.2

    • Added: Holded API v2 support. The API version is now auto-detected from the key’s shape (keys prefixed with pat_ use v2, existing keys keep using v1) — both versions work through the same connector with no new setting.
    • Enhanced: “API Connection Status” badge and entry success notes now show the detected Holded API version (e.g. “Connected (Holded v2)”) instead of a generic “(Holded)”.
    • Fixed: CRMLIB_HOLDED::login() and list_modules() signature mismatch with the CRMLIB_Abstract contract, which caused a PHP fatal error on the Holded feed settings page in production.
    • Fixed: Holded v2 field names (e.g. bill_address, trade_name, is_person) are now translated from the existing v1 camelCase field IDs, so feeds configured before the v2 migration keep working unmodified.
    • Fixed: Clientify API v2 contact merge returning a 409 conflict when matching by taxpayer_identification_number; the field is now supported as a search/merge key.
    • Fixed: Clientify API v2 now sends email inside the emails array (type Main) instead of a top-level field, matching the v2 schema.
    • Fixed: Clientify API v2 GET requests now always include the required fields parameter, even when other query params are already set.
    • Tests: Added PHPUnit coverage for both Holded API v1 and v2 using fixtures captured from real sandbox accounts.

  5. FormsCRM 4.4.1

    • Fixed: GravityForms {label:X} merge tag returning wrong label when select/radio fields have duplicate values.
    • Fixed: Merge strategy field not showing correctly.

  6. FormsCRM 4.4.0

    • Enhanced: Added support to GravityForms and Clientify to update strategy in the feed. You can choose between update if contact exists or create new contact always.
    • Enhanced: Added CRMLIB_Abstract base class to unify the CRM library interface (create_or_update_entry, list_fields_search_entry, determine_search_by) across all integrations.
    • Enhanced: GravityForms entry notes now include the action taken (created/updated) and the merge strategy field used.
    • Fixed: Clientify API version now propagated consistently to deals and products requests instead of using hard-coded strings.
    • Fixed: Improved build_error_message() to handle WP_Error objects and parse standard API error keys (error, detail, message).
    • Fixed: Clientify GDPR checkbox value in Contact Form 7 now normalized to ‘1’ (accepted) or ” (not accepted), regardless of the checkbox label language.
    • Add a notice to recall to review the plugin FormsCRM.
    • Added: Support for JetFormBuilder forms plugin with full field mapping and global settings integration.
    • Added: Support to FormsCRM UTM Tracker plugin to send UTM parameters from the cookie to the CRM as merge vars.
    • Fixed: API Clientify error not add null values in custom fields.
    • Fixed: Error in CF7 value expert.
    • Fixed: Login error depending on the CRM, now it shows the error message from the CRM in the settings page.
    • Fixed: Elementor not getting correctly the module from settings.
    • Fixed: Normalize boolean CRM fields to standardized values for Clientify.
    • Fixed: CF7 “Saving…” spinner was always visible because wp_kses strips display:none from inline styles; moved visibility control to CSS class.
    • Fixed: Brevo list_modules pagination now returns all lists instead of only 10 by properly sending limit/offset parameters and accumulating paginated results.

  7. FormsCRM 4.3.3

    • Added: Smart support for Clientify API v2 and v1 with enhanced login response handling and error messages.
    • Fixed: Elementor Forms field mapping only processed the first occurrence when multiple CRM fields mapped to the same form field; now all mappings are applied correctly.
    • Tests: Added unit tests for Elementor and Contact Form 7 merge vars field mapping.
    • Fixed: CF7 GDPR checkbox value sent as field name instead of boolean when unchecked, causing gdpr_accept to always be true in Clientify.
    • Fixed: Error logs page not working properly.

  8. FormsCRM 4.3.2

    • Migrated: Clientify to API v2 (api-plus.clientify.com/v2): login me/, custom fields object_type filter, deal creation with ID-based refs and inline products (v2 schema).
    • Added: Clientify contact marketing_status, pipeline ID/stage name, and Email Main/Phone Main field types. It defaults to Marketing Contact (2).
    • Fixed: HTTP PUT via wp_remote_request(), consistent wp_remote_retrieve_body() for errors, pipeline_desc mapping.
    • Fixed: GravityForms widget sending leads twice when viewing or editing an entry.
    • Fixed: WPForms > Connections was not working correctly.

  9. FormsCRM 4.3.1

    • Enhanced: Support for GravityPDF merge tags in GravityForms.
    • Fixed: File upload field not sending correctly in GravityForms.
    • Fixed: Brevo duplicate contact error when email already exists. Contacts are now updated instead of returning an error.
    • Fixed: PHP warning when Brevo returns 204 No Content response for updated contacts.

  10. FormsCRM 4.3.0

    • Added: API connection status indicators across all form integrations (GravityForms, WPForms, Elementor, Contact Form 7, WooCommerce).
    • Added: Visual connection status badges with color coding – green (connected), red (error), gray (not configured).
    • Added: Real-time connection validation with detailed error messages when authentication fails.
    • Added: Markdown Export feature for GravityForms entries with single and bulk export capabilities.
    • Added: Export entries as clean, well-structured Markdown files with full field type support.
    • Added: Bulk export creates ZIP file with multiple entry Markdown files for easy sharing.
    • Added: Automatic retry system with up to 3 attempts at 1-hour intervals, visual progress counter, and smart cancellation when entries succeed or are deleted.
    • Added: Error Log feature with comprehensive tracking, filtering by status/CRM, detailed error views, resend capability, and pagination for easy management.
    • Enhanced: Contact Form 7 module selection now auto-saves configuration with visual feedback.
    • Enhanced: Responsive AJAX-based interface with color-coded status badges and synchronized manual/automatic retry system.
    • Enhanced: Feed connection status in Forms list in Gravity Forms.
    • Fixed: Resend button missing in Gravity Forms Entries view.
    • Enhanced: Added feed selector in Resend Entry widget to choose between all feeds or individual feed.
    • Added date conversion in Clientify for birthday field.
    • Hotfix: Error not sending correctly entry id in webhook.

202511 releases

  1. FormsCRM 4.2.1

  2. FormsCRM 4.2.0

    • Enhanced: New design for the settings page.
    • Enhanced: Dedicated menu for FormsCRM settings.
    • Improved: Added new tests for more consistent code coverage.
    • Fixed: Fatal error in formscrm_debug_email_lead function.

  3. FormsCRM 4.1.0

    • Enhanced: Complete redesign of the settings page with modern UI and improved UX.
    • Enhanced: New color scheme with cyan-to-purple gradient for better visual appeal.
    • Enhanced: Modern tab navigation system for better organization of settings and license management.
    • Enhanced: Responsive grid layout for forms and CRM integrations display.
    • Enhanced: Improved cards design with hover effects and smooth transitions.
    • Added: Slack integration for real-time error notifications via Incoming Webhook.
    • Enhanced: Slack notifications include comprehensive information (site, form, CRM, error, lead preview).
    • Enhanced: Slack messages use a compact, single-line format for quick scanning.
    • Enhanced: All form integrations (Gravity Forms, WPForms, Elementor, Contact Form 7, WooCommerce) now include form context in error reports.
    • Added: 10 comprehensive unit tests for Slack notification functions.
    • Added: Test utility for manually testing Slack notifications (tests/test-slack.php).
    • Added: Custom email option for error notifications – Configure specific emails to receive error reports.
    • Enhanced: Error email notifications now include site information (name, URL, timestamp).
    • Enhanced: Error emails now show detailed form information (type, ID, name, entry ID).
    • Enhanced: Professional HTML email template with color-coded sections for better readability.
    • Enhanced: Complete technical details in error emails (API URL and JSON request) for easier debugging.
    • Improved: All form integrations (Gravity Forms, WPForms, Elementor, Contact Form 7, WooCommerce) now send enhanced error information.

  4. FormsCRM 4.0.6

    • Added: Support Deals tags in Clientify.
    • Fixed: Format of webhook url in GravityForms.
    • Fixed: PHP 7.4 compatibility issues.

  5. FormsCRM 4.0.5

    • Fixed: CF7 custom fields with select fields not sending.
    • Added: Expert Mode.
    • Fixed: Fatal errors in CF7.

  6. FormsCRM 4.0.4

    • Added: Webhook to send form data received from CRM in GravityForms.
    • Added: Automatic tests for robust testing and quality code.

  7. FormsCRM 4.0.3

    • Enhaced: Add Pipeline name to improve Clientify pipeline implementation in Forms.
    • Fixed: Autoassigment in Clientify not added in contacts module.
    • Updated developer dependencies.

  8. FormsCRM 4.0.2

    • Added: Expected closure date for Deals in Clientify.
    • Fixed: Elementor Forms Fields and values not sending.
    • Fixed: Warnings messages in load_plugin_textdomain.

  9. FormsCRM 4.0.1

    • Fixed: Elementor Forms with URL Odoo not working.

  10. FormsCRM 4.0.0

    • Added: New connector for Elementor Forms.
    • Added Brevo Email Marketing.
    • Added field autoassignment_users in Clientify (String with the list of usernames separated by comma (,) to apply the autoassignment).
    • Added Product SKUs in Opportunity in Clientify.
    • Added disclaimer field in Clientify.
    • Added in Clientify different types of Emails: work, personal, other and main. Phones: main, mobile, work, home, fax, other.
    • Added show Login errors from API.

  11. FormsCRM 3.15.7

    • Fixed: Fixed manage contact websites in Clientify.
    • Fixed: Better management of Clientify API errors.

202415 releases

  1. FormsCRM 3.15.3

    • Added: Logs connection and entry created with WPForms in the form entry always.

  2. FormsCRM 1.2.1

  3. FormsCRM 3.15.6

    • Added: Search contact or lead in Holded by email.

  4. FormsCRM 3.15.5

    • Added: Dynamic values in WPForms.

  5. FormsCRM 3.15.4

    • Fixed: Connection WPForms field date was not formatting to YYYY-MM-DD.

  6. FormsCRM 3.15.2

    • Fixed: Sometimes gives Fatal error in WooCommerce Settings page.

  7. FormsCRM 3.15.1

  8. FormsCRM 3.15.0

  9. FormsCRM 3.14.0

  10. FormsCRM 3.13.5

  11. FormsCRM 3.13.4

  12. FormsCRM 1.2.0

  13. FormsCRM 3.13.3

  14. FormsCRM 3.13.2

  15. FormsCRM 1.1.0

20239 releases

  1. FormsCRM 3.13.1

  2. FormsCRM 3.13.0

  3. FormsCRM 3.12.4

  4. FormsCRM 3.12.3

  5. FormsCRM 3.12.2

  6. FormsCRM 3.12.0

  7. FormsCRM 3.11.0

  8. FormsCRM 3.10.0

  9. FormsCRM 3.9.2

202212 releases

  1. FormsCRM 3.9.1

  2. FormsCRM 3.9.0

  3. FormsCRM 3.8.2

  4. FormsCRM 3.8.1

  5. FormsCRM 3.8.0

  6. FormsCRM 3.7.3

  7. FormsCRM 3.7.2

  8. FormsCRM 3.7.1

  9. FormsCRM 3.7.0

  10. FormsCRM 3.7.0-beta.3

  11. FormsCRM 3.6

  12. FormsCRM 3.5.1

20217 releases

  1. FormsCRM 3.5

  2. FormsCRM 3.4

  3. FormsCRM 3.3

  4. FormsCRM 3.2

  5. FormsCRM 3.1.1

  6. FormsCRM 3.1

  7. FormsCRM 3.0

Questions about FormsCRM’s releases

What is the latest version of FormsCRM?

4.4.5, released on Nov 4, 2026 (4 days ago). It’s tested up to WordPress 7.1.4.

How often is FormsCRM updated?

14 releases in the last year, about one every 27 days. Its first release on WordPress.org dates from June 2021.

Know when your rivals ship

Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.

Start free

Release dates come from the day each version’s folder was made in FormsCRM’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.