Migrate Clientify integration from API v1 to API v2

[davidperezgar]

Migrates the Clientify CRM integration from the legacy API v1 to the new API v2 (api-plus.clientify.com/v2). This update includes endpoint changes, schema updates, and several fixes for reliability and data integrity.

Fixes #163.

Changes

• API v2 migration — Updated all Clientify endpoints: login via me/, custom fields now filter by object_type, deal creation uses ID-based references with inline products following the v2 schema
• marketing_status default — Contacts now default to marketing_status = 2 (Marketing Contact) when the field is not explicitly set, avoiding API rejections on contact creation
• Pipeline improvements — Support for pipeline ID/stage name resolution and pipeline_desc field mapping
• Email Main / Phone Main — Added support for Email Main and Phone Main field type mapping
• HTTP method fix — Replaced incorrect HTTP verbs with wp_remote_request() using PUT; unified response handling via wp_remote_retrieve_body() for error paths
• GravityForms widget fix — Resolved a bug where leads were being sent twice when viewing or editing an existing entry
• Code cleanup — Removed redundant blank lines and applied DRY refactoring across the Clientify class
• readme.txt — Updated changelog for version 4.3.2 with clarification that marketing_status defaults to Marketing Contact (2)

Benefits

• Compatibility with Clientify's current API v2, preventing broken connections for all users
• Contacts are created successfully even when marketing_status is not explicitly configured in the feed
• Reduced risk of duplicate CRM submissions from GravityForms entry edits
• Cleaner, more maintainable codebase via DRY improvements

Testing Instructions

1. Go to WordPress Admin → FormsCRM → Settings and enter valid Clientify API v2 credentials
2. Open a form (e.g. Gravity Forms) with a Clientify feed configured
3. Submit the form and verify the contact is created in Clientify under the Marketing Contact status
4. Edit an existing GravityForms entry and confirm no duplicate lead is sent to Clientify
5. Create a feed with pipeline mapping and verify the deal is created with the correct pipeline ID and stage
6. Submit a form without marketing_status explicitly mapped — confirm it defaults to Marketing Contact (2) in Clientify

Checklist

• Code follows WordPress Coding Standards
• Self-reviewed the code
• Added necessary comments
• No new linter errors

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}