BugWP logo BugWP
Back to Community
Home / Community / General

Troubleshooting HubSpot Integration Issues in Forminator Forms

17 threads Sep 16, 2025

Content

Integrating your Forminator forms with HubSpot is a powerful way to manage leads and automate your marketing. However, users often encounter specific issues that prevent data from syncing correctly. Based on common community reports, this guide addresses the most frequent HubSpot integration problems and their solutions.

Common HubSpot Integration Issues

Users typically face a few recurring challenges when connecting Forminator to HubSpot:

  • Connection Problems: Difficulty establishing or re-establishing a connection, especially after moving from a staging to a live site.
  • Field Mapping Errors: HubSpot rejects data because the Forminator field identifier (often a slug) does not match the expected HubSpot property name.
  • Conditional Logic Conflicts: Inability to map multiple conditional fields (e.g., phone1, phone2) to a single HubSpot property.
  • Ticket Creation Failures: Errors like "Failed to process request : Property values were not valid" when trying to create HubSpot tickets, even though contact creation works.
  • Incomplete Data Sync: Contacts appear in some HubSpot lists but not others, or the data synced is incomplete (e.g., using an email address for a name field).

Why These Issues Happen

These problems usually stem from a few key areas:

  • API Key and Reconnection: Disconnecting and reconnecting an integration can sometimes cause authentication issues if API keys or app credentials are not perfectly aligned.
  • HubSpot's Property Requirements:
    • HubSpot requires data to be sent to specific, pre-defined internal property names. If Forminator sends a field labeled text-1 but HubSpot expects firstname, the mapping will fail.
  • Integration Limitations: The native integration is designed primarily for creating contacts. Creating tickets or submitting data to pre-existing HubSpot forms often requires more complex property mapping that may not be fully supported out-of-the-box.
  • Conditional Field Handling: The integration may not have a built-in method to handle two different source fields mapping to one destination property based on conditional logic.

How to Troubleshoot and Resolve These Issues

1. Re-establishing a Connection

If you cannot reconnect to HubSpot after disconnecting:

  • Go to your HubSpot account and ensure the API key or OAuth app you are using is still active and valid.
  • In your WordPress dashboard, navigate to Forminator > Integrations > HubSpot and click "Add New Account." Carefully follow the re-authentication process.
  • Clear your WordPress cache and any server-level cache after reconnecting.

2. Fixing Field Mapping Errors

To ensure Forminator fields map to the correct HubSpot properties:

  • In HubSpot, identify the exact internal property names for the fields you want to use (e.g., firstname, lastname). You can find this in your HubSpot settings under "Properties."
  • In your Forminator form, edit the HubSpot integration. For each field, use the dropdown to map your Forminator field to the correct HubSpot property. You cannot manually type a custom property name; you must select it from the list of available HubSpot properties.
  • If the correct property does not appear in the dropdown, you may need to create it first in your HubSpot account.

3. Handling Conditional Fields

There is no direct way to map two fields to one HubSpot property. A common workaround is:

  • Use a hidden field in your Forminator form.
  • Set up your form's logic to populate this hidden field with the value from either phone1 or phone2 based on the user's selection.
  • Map this single hidden field to the phone property in HubSpot.

4. Addressing Ticket Creation Failures

The error "Property values were not valid" indicates a mapping problem with the ticket properties.

  • When setting up ticket creation in the Forminator integration, ensure every required property for a ticket in HubSpot is properly mapped. An empty but required property will cause this error.
  • Double-check that the data types match (e.g., you are not trying to pass text into a date field).

5. Verifying Data Sync

If contacts are not appearing in the correct lists:

  • HubSpot workflows often manage list membership. The integration might be creating the contact correctly, but a separate workflow rule might be preventing it from being added to a specific list. Review your HubSpot workflows and active lists.
  • Check for error logs in Forminator. Go to Forminator > Submissions for your form and see if any submissions show a failed integration attempt, which may provide a more specific error message.

When to Seek Further Help

If these steps do not resolve your issue, the community can often help if you provide specific details. When asking for help, be prepared to share:

  • The exact error messages you see.
  • Screenshots of your Forminator field settings and your HubSpot integration mapping setup.
  • Whether the issue occurs consistently or intermittently.

Remember, for complex customizations like creating a true HubSpot "form submission" instead of just a contact, custom development may be required beyond the plugin's standard feature set.

Related Support Threads Support