HubSpot Integration

1. From the main Ivorey™ menu, go to Workflows > open an existing workflow, or click [+ Create Workflow] > and select [Start from Scratch]

2. At the top of your workflow, click [+ Add New Trigger] > search for HubSpot > and select the [New Contact Created] trigger (this fires when a new contact is created in HubSpot):

   1. Click the [Connect your Account] button, to integrate HubSpot into Ivorey™ > and sign into your HubSpot account

   2. (optional) Add Filters to narrow which contacts enrol (e.g. lifecycle stage or source property), so unrelated contacts don't trigger the workflow

3. Click the [Find New Records] button, to test the trigger and confirm that HubSpot contact data is coming through successfully

4. Once successful, click [Save Trigger]

5. Click the [+] button to add any actions you want - this is what you want to happen in Ivorey™ when the HubSpot trigger fires - for example:

   1. Add Tag - apply a tag to the contact's record in Ivorey™

   2. Send Internal Notification - notify yourself or a team member

   3. Add to Workflow - enrol the contact into another workflow (e.g. a nurture sequence you have set up in Ivorey™)

6. Add as many actions as needed > toggle the workflow to [Publish] at the top right corner > and click [Save]

7. Test your workflow by completing the trigger (i.e. creating a new contact in HubSpot) > then check the [Execution Logs] tab inside your workflow to confirm there are no errors with any of the workflow steps

1. From the main Ivorey™ menu, go to Workflows > open an existing workflow, or click [+ Create Workflow] > and select [Start from Scratch]

2. Inside the workflow, click [+ Add New Trigger] > search for or select a trigger (this is what happens in Ivorey™ that should trigger the HubSpot action), for example:

   1. When there is a Form Submitted

   2. When a Pipeline Stage Changed

3. Click the [+] button to add a new action > search for HubSpot > and select an action:
   

   Note: If you haven’t connected HubSpot yet, click the [Connect your Account] button at the top of the action, to integrate HubSpot into Ivorey™ > and sign into your HubSpot account

   1. Create Contact - creates a new contact in HubSpot:

      1. Map the fields for Email, First Name and Last Name > click the 🏷 tag icon next to each field to select a custom value (e.g. Contact > First Name)
         
         Note: Using custom values allows Ivorey™ to send the contact’s details from the Ivorey™ CRM to HubSpot, in order to create the contact.

      2. (optional) Map fields for Phone, Company and any other custom HubSpot fields

   2. Find Contact - looks up an existing contact in HubSpot by name, ID or email and pulls in their data to use in following workflow actions
      
      Note: To avoid creating duplicate contacts in HubSpot, we recommend placing a Find Contact step (searching by email) before your Create Contact action. Then use the If/Else action to branch your workflow and skip the contact creation step, if an existing HubSpot contact is found.

4. Add any other actions needed > toggle the workflow to [Publish] at the top right corner > and click [Save]

5. Test your workflow by completing the trigger (e.g. submit a test form) > then check the [Execution Logs] tab inside your workflow to confirm there are no errors

No. The integration works on the free HubSpot CRM tier. Some HubSpot-side features, such as advanced automation and certain custom property types, require a paid HubSpot plan. Those limitations come from HubSpot itself, not from this integration.

Yes. It's powered by a HubSpot webhook, so workflows enrol within seconds of a new contact being created in HubSpot.

Yes. The New Contact Created trigger fires for any new contact in HubSpot, regardless of where it came from, whether that's a HubSpot form, a sales rep's manual entry, or another integration. Use trigger filters to narrow this down by source or lifecycle stage if needed.

Yes. Any property defined on the HubSpot Contact object, standard or custom, can be mapped in the action. Make sure the property exists in HubSpot before mapping it.