Tell me what you need 
Guide · HubSpot integrations

How to connect a WordPress form to HubSpot, and which way to choose

There are three realistic ways to get website enquiries into HubSpot, and the right one depends on the forms you already have. Here is how I’d choose, and the checks that stop leads quietly going missing.

  1. 1. Decide what should happen to a new enquiry

    Before choosing a tool, write down what you want to happen when someone submits the form: a new contact created, a deal opened, an owner assigned, a follow-up email sent. The connection is only useful if the right things happen at the other end.

    List each form and the fields it collects, then decide which HubSpot property each field belongs in. Mismatched fields are the most common reason a connection “works” but the data is unusable.

  2. 2. Option one: HubSpot’s own WordPress plugin

    HubSpot provides an official WordPress plugin. You can build forms inside HubSpot and embed them on your pages, and the plugin can also add HubSpot’s tracking code to the site. Submissions arrive in HubSpot directly, with no extra tool in between.

    This is the simplest route when you’re happy to use HubSpot forms on the site. The trade-off is that the form’s design and behaviour live in HubSpot rather than in your existing form plugin.

  3. 3. Option two: connect your existing form plugin

    If you already have forms built in a plugin such as Gravity Forms, WPForms or Contact Form 7, there are usually add-ons or integration services that pass submissions to HubSpot, and some plugins offer a HubSpot connection built in. What’s available varies by plugin and by licence, so check your plugin’s current documentation.

    This keeps your existing forms and styling, but adds another moving part: a plugin or service that has to stay connected and up to date.

  4. 4. Option three: custom code

    For unusual requirements, such as a form that creates several records, applies business rules or sends data from a WooCommerce order, a small piece of custom code can send the submission to HubSpot’s API.

    It’s the most flexible option and the most to maintain, so it’s worth choosing only when the first two can’t do the job. It also needs proper error handling, covered below.

  5. 5. Keep the tracking connection in mind

    HubSpot’s tracking code sets a cookie that links a form submission to the visitor’s earlier page views and traffic source. If your integration doesn’t pass that information through, the contact is created but you lose where they came from.

    Check that the tracking code is on the site and that your chosen method passes it on if you rely on source reporting. Tracking cookies also need to be handled in line with UK consent rules.

  6. 6. Plan for failure

    Connections fail: a key expires, HubSpot is briefly unavailable, a required property is renamed. Decide what should happen when a submission can’t be delivered. Never let it vanish silently.

    A good minimum is to keep the notification email going as a backup and to record failed deliveries somewhere you will see them. A lead that reaches your inbox but not HubSpot is annoying. A lead that reaches neither is lost.

  7. 7. Test with real submissions

    Submit every form on the live site and check the contact in HubSpot: fields in the right properties, owner assigned, workflows triggered, source recorded. Test with an email address that already exists as a contact as well, because that’s when duplicates and overwritten values appear.

    Then test the failure case by temporarily breaking the connection on a copy of the site, so you know what you’d see if it happened for real.

Need forms connected to HubSpot?

Tell me what should happen when someone submits a form and include your website address. I’ll reply with any questions and tell you what I think it needs.