CF7 to HubSpot \u2192 Forms<\/strong>, open a form, add the HubSpot objects it should create, map the fields and turn Sync on.<\/li>\n<\/ol>\n\nWordPress Multisite:<\/strong> do not network-activate. Activate the plugin on each site that needs it; each site connects its own HubSpot account.<\/p>\n\n\n\nHow do I get a HubSpot access token (service key)?<\/h3><\/dt>\nHubSpot no longer lets you create new private apps (since 28 September 2026 for new accounts, and 26 October 2026 for existing ones). Use a service key instead; a token from an existing private app keeps working.<\/p>\n\n
\n- Log in to HubSpot as a super admin and create a service key: https:\/\/developers.hubspot.com\/docs\/apps\/developer-platform\/build-apps\/authentication\/account-service-keys<\/li>\n
- Give it these scopes: crm.objects.contacts.read and .write, crm.objects.companies.read and .write, crm.objects.deals.read and .write, crm.objects.tickets.read and .write, crm.schemas.contacts.read, crm.schemas.companies.read, crm.schemas.deals.read, forms, files.write and communication_preferences.read. (A private app token with the older
tickets<\/code> and files<\/code> scopes keeps working.)<\/li>\n- If you use journey (custom behavioral) events (cf7_form_submitted, cf7_form_synced, cf7_form_sync_failed), also add analytics.behavioral_events.send<\/strong> and behavioral_events.event_definitions.read_write<\/strong>, create matching custom event definitions in HubSpot, and enable Journey events in the plugin settings.<\/li>\n
- Paste the key into CF7 to HubSpot \u2192 Settings \u2192 Access token and click Connect. The token is saved only after HubSpot accepts it.<\/li>\n<\/ul><\/dd>\n
Does it work with the free HubSpot CRM?<\/h3><\/dt>\nContacts, companies, deals, tickets and HubSpot forms use HubSpot's standard CRM and Forms APIs. Journey events use HubSpot custom events, which are not part of every HubSpot plan; leave them off if your plan does not have them.<\/p><\/dd>\n
Can I send one form to several HubSpot objects?<\/h3><\/dt>\nYes. On the form's mapping screen click \"Add an object\" and pick a Company, Deal or Ticket (or another Contact). Each object has its own field mapping and can be associated with an object above it.<\/p><\/dd>\n
Will it create duplicate contacts?<\/h3><\/dt>\nA Contact object has a switch: update the contact with the same email, or always create a new one.<\/p><\/dd>\n
Can I put deals into a specific HubSpot pipeline?<\/h3><\/dt>\nYes. Add a Deal object to the form's mapping and choose its pipeline and deal stage.<\/p><\/dd>\n
Can I send UTM parameters and hidden fields?<\/h3><\/dt>\nYes. Any Contact Form 7 field, hidden fields included, can be mapped to a HubSpot property. UTM parameters and ad click ids are added only to the properties you map them to; turn on \"Attribution cookies\" to keep them from the landing page until the form is sent.<\/p><\/dd>\n
Should I send to HubSpot objects or to a HubSpot form?<\/h3><\/dt>\nSend to a HubSpot form when you want HubSpot's form features: form-based workflows, form submission reports and the visitor's page history on the contact. Send to objects when you need companies, deals or tickets, or several linked records from one submission.<\/p><\/dd>\n
Where do I see why a submission did not reach HubSpot?<\/h3><\/dt>\nOpen CF7 to HubSpot \u2192 Logs. Click an entry to see what HubSpot answered and which properties it rejected. Personal data is masked; use \"Copy details\" to share the entry with support.<\/p><\/dd>\n
HubSpot shows each submission twice<\/h3><\/dt>\nHubSpot's own tracking code can also collect Contact Form 7 submissions. In HubSpot, turn off \"Collect data from website forms\" under the non-HubSpot forms settings.<\/p><\/dd>\n
Do visitors wait for HubSpot when they submit a form?<\/h3><\/dt>\nOnly if background processing is off. Turn it on in Settings and the form answers at once while the HubSpot requests run in the background.<\/p><\/dd>\n
How do I get help or suggest a feature?<\/h3><\/dt>\nPost in the support forum of this plugin, or write to hello@procoders.tech.<\/p><\/dd>\n
How do I change what the plugin sends to HubSpot from my own code? (developer hooks)<\/h3><\/dt>\nSince 1.4.1 the plugin has developer hooks. They are for people who write PHP; there is no setting for them in the admin.<\/p>\n\n
\ncf7hs_object_payload<\/code> (filter, $data, $module, $form_id, $context<\/code>): change the HubSpot properties of one object just before it is written. $module<\/code> is contacts<\/code>, company<\/code>, deals<\/code> or tickets<\/code>, or the HubSpot form GUID when the form is sent to a HubSpot form. Register with 4 accepted arguments to receive $context<\/code> (index<\/code>, action<\/code>, post_id<\/code>, request<\/code>, async<\/code>, attempt<\/code>).<\/li>\ncf7hs_object_synced<\/code> (action, $record_id, $module, $form_id, $outcome, $context<\/code>): an object was created or updated. Register with 5 accepted arguments to receive $context<\/code>. $record_id<\/code> is an integer, and 0 for a HubSpot form target.<\/li>\ncf7hs_object_sync_failed<\/code> (action, $module, $form_id, $outcome, $context<\/code>): an object failed or was skipped. Register with 4 accepted arguments to receive $context<\/code>.<\/li>\ncf7hs_submission_completed<\/code> (action, $status, $form_id, $outcomes, $context<\/code>): the submission reached its final outcome. $status<\/code> is synced<\/code> when the first object was written, otherwise failed<\/code>. Register with 4 accepted arguments to receive $context<\/code>. It does not fire when consent blocks the submission.<\/li>\ncf7hs_is_form( $form_id, $id_or_hash )<\/code>: true when the form is the one with that post id or that shortcode hash (the 7 or more characters in [contact-form-7 id=\"2f24e69\"]<\/code>).<\/li>\n<\/ul>\n\nExample: set the lifecycle stage to customer for contacts from one form only.<\/p>\n\n
add_filter( 'cf7hs_object_payload', 'my_cf7hs_customer_stage', 10, 4 );\nfunction my_cf7hs_customer_stage( $data, $module, $form_id, $context ) {\n if ( 'contacts' === $module && cf7hs_is_form( $form_id, '2f24e69' ) ) {\n $data['lifecyclestage'] = 'customer';\n }\n return $data;\n}\n<\/code><\/pre>\n\nThe value is written in the same request that creates or updates the contact, so it costs no extra API call. For a form sent to a HubSpot form, $module<\/code> is the HubSpot form GUID, so test that instead of 'contacts'<\/code>: if ( 'your-hubspot-form-guid' === $module && cf7hs_is_form( $form_id, '2f24e69' ) )<\/code>.<\/p>\n\nLifecycle stage notes: use the internal value (customer<\/code>, not \"Customer\"). Custom stages have numeric ids; read the options of the lifecyclestage<\/code> property in HubSpot to find them. HubSpot only moves a lifecycle stage forward through the API and forms, so a contact who is already past customer<\/code> stays where they are.<\/p>\n\nThings to know:<\/p>\n\n
\n- Keep callbacks idempotent. With asynchronous submissions the same object can reach your callback again on a retry (see
$context['attempt']<\/code>); cf7hs_object_sync_failed<\/code> can repeat, cf7hs_object_synced<\/code> effectively fires once per object. With async, uploaded files are attached after the objects are written, so cf7hs_object_synced<\/code> can run before the files are attached.<\/li>\ncf7hs_submission_completed<\/code> says failed<\/code> when the first object was not written. Later objects may still have been written, and no retry follows then. $outcomes<\/code> lists every object and is empty when the final attempt threw an error. A form whose first object has no mapped fields fires no hooks.<\/li>\n- Return values of the filter:
true<\/code>\/false<\/code> are sent as true<\/code>\/false<\/code>, other scalars as text, and ''<\/code> clears the property in HubSpot. Arrays and other non-scalar values are dropped with a warning in the log. Date and datetime values are sent as epoch milliseconds in a string (for example 1760832000000<\/code>), which is what HubSpot expects, so a callback that sets a date property should send the same format. A multi-checkbox is one value joined with ;<\/code>. File fields and the HubSpot tracking context are not passed to the filter and cannot be changed by it.<\/li>\n- If a callback throws an error it is caught and logged as a warning, and the submission goes on. For the filter, the unfiltered properties are then sent, so changes made by earlier callbacks are discarded too.<\/li>\n
- Warning about consent: the plugin checks consent before the filter runs. If your callback changes
email<\/code> or a consent property, the new value is sent without that check.<\/li>\n- Arguments of these hooks are only ever added at the end; new keys may appear in
$context<\/code>. cf7hs_is_form<\/code> with a digit-only string of 7 or more characters matches the post id first, so it can differ from how Contact Form 7 resolves the same value.<\/li>\n<\/ul><\/dd>\nOther filters<\/h3><\/dt>\ncf7hs_log_ttl_days sets how many days log entries are kept (30 by default). cf7hs_error_email_throttle_seconds<\/code> sets the window in which repeated error emails are counted instead of sent (one hour by default).<\/p><\/dd>\nWhere is the source of the compiled admin CSS?<\/h3><\/dt>\nThe admin stylesheets in src\/Admin\/Assets\/build\/ are compiled from the SCSS in src\/Admin\/Assets\/scss\/, which ships with the plugin. They are built with Dart Sass 1.105.1 and @wordpress\/base-styles 13.3.0:\n sass --no-source-map --style=compressed --load-path=node_modules src\/Admin\/Assets\/scss:src\/Admin\/Assets\/build<\/p><\/dd>\n\n<\/dl>\n\n\n
1.4.2<\/h4>\n\n\n- Readme rewritten: shorter description, setup steps, installation from the Plugins screen, and new FAQ answers (free HubSpot CRM, duplicate contacts, UTM and hidden fields, HubSpot form or objects). The plugin code is unchanged.<\/li>\n
- Changelog entries before 1.4.0 moved to changelog.txt.<\/li>\n<\/ul>\n\n
1.4.1<\/h4>\n\n\n- Developer hooks:
cf7hs_object_payload<\/code> filters the HubSpot properties of each object before it is written (contacts, companies, deals, tickets and HubSpot forms), cf7hs_object_synced<\/code> and cf7hs_object_sync_failed<\/code> fire after each object, and cf7hs_submission_completed<\/code> fires once per submission with its final outcome. They behave the same with and without asynchronous submissions.<\/li>\ncf7hs_is_form( $form_id, $id_or_hash )<\/code> matches a form by post id or by the hash in its shortcode.<\/li>\n- A callback that throws an error is logged as a warning instead of breaking the submission or causing an asynchronous retry.<\/li>\n
- Settings and the FAQ list the exact scopes a HubSpot service key needs: read and write for contacts, companies, deals and tickets, schema reads for contacts, companies and deals, forms, files.write and communication_preferences.read. A private app token with the older scopes keeps working.<\/li>\n
- A deal's pipeline and stage are never sent with any other HubSpot object, even if a form's settings were saved outside the mapping screen.<\/li>\n
- Fixed: a field mapped to \"Attachments\" was also sent to HubSpot as a property named
attachment_field<\/code>. On a portal without such a property HubSpot rejected the whole record, so the contact (or deal, company, ticket) was not created. The upload is now only attached to the record.<\/li>\n<\/ul>\n\n1.4.0<\/h4>\n\n\n- Send one form to several HubSpot objects: Contact, Company, Deal and Ticket, each with its own mapping and an association with an object above it. A HubSpot form target stays a single object.<\/li>\n
- Contacts: one switch chooses between updating the contact whose email already exists and always creating a new one.<\/li>\n
- Uploaded files are attached only to the objects whose mapping includes them, in sync and async mode.<\/li>\n
- Consent is checked on the CRM path too: a CRM form can choose the subscription types it enforces, and a submission is blocked when the email is unsubscribed or HubSpot cannot be asked.<\/li>\n
- Opt-in first-touch attribution cookies that wait for marketing consent through the WP Consent API.<\/li>\n
- The access token is saved only after HubSpot accepts it.<\/li>\n
- Logs move from debug.log to a database table with personal data masked, kept for 30 days. The Logs screen has search, result tabs, a form filter, and entries that open under their row.<\/li>\n
- Error emails carry a masked summary and a link to the log entry; repeats of the same kind within an hour are counted and summarised instead of mailed one by one.<\/li>\n
- Redesigned admin screens in the WordPress look: the forms list (status tabs, search, bulk pause and resume), the mapping screen and Logs, with layouts for phones.<\/li>\n
- Uninstall (when \"Delete data on uninstall\" is on) also removes the log table and the email throttle data.<\/li>\n
- Requires WordPress 5.9 or later (PHP 8.0 was already required).<\/li>\n<\/ul>\n\n
Older releases: see changelog.txt in the plugin folder.<\/p>","raw_excerpt":"Send Contact Form 7 submissions to HubSpot: contacts, companies, deals, tickets or HubSpot forms. File uploads, consent checks and logs.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/191192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=191192"}],"author":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/procoders"}],"wp:attachment":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=191192"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=191192"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=191192"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=191192"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=191192"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=191192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}