Hubspot is an advanced CRM for sales and marketing teams, but it can also help you move faster with tools such as Parallel in one place.
With this guide, we want to help you synchronize Parallel with your CRM to update the status of your deals automatically with the events that take place in Parallel.
👉 Want to try the automation directly on Zapier?
|
Here's how you can update a Hubspot deal with a Parallel event:
Preparing the integration
Before starting the integration, there are two previous tasks to perform in our Parallel and Hubspot accounts.
a) Task 1: Create a new property in Hubspot
Create a new property in the HubSpot object (usually deal or contact) where we want to log the event.
In case you need it, the Hubspot team explains how to create and edit properties in this article.
Note: You will need admin permissions to create new properties in Hubspot. |
b) Task 2: Add an internal field in the parallel template to store HubSpot dealId.
Select the parallel template you want to automate.
Create a Short replies field for the HubSpot deal Id.
Set it as an internal field.
Add a reference to the internal field. The reference will be used as the key of the results you get in Zapier.
This field helps Zapier relate Parallel events with the HubSpot deal, so make sure to complete it when starting a parallel. You can fill it out manually or create another Zap that pre-fills it automatically (for example, when a deal reaches a particular stage).
Selecting a Parallel event trigger
Create a new Zap
In the trigger step, select Parallel from within the apps.
Choose Petition Event as the triggering event.
Continue and select your account (you can associate a Parallel account using an API token if you don't have any associations yet).
Now in Set up trigger,
Event types: Choose the event from which you want to get updates.
From template ID: Select the process template you want to get notifications from within Hubspot. If you can't find a template, you can add its id, by copying it from the URL.
Additional petition fields: Include the "The replies of the petition as key-value object". We will need this later to access the internal deal id field.
When you finish, your trigger should look like this:
Test the trigger and confirm that you have access and the correct information.
Add Hubspot action
Add an action and select Hubspot.
Select the Update Deal event.
Continue and select your account (follow these steps if you don't have a Hubspot account associated with Zapier).
Now in Set up action:
Object Id: Select "Petition replies Deal Id". This will access the deal id entered in the internal field.
Search for your new property and add the message you wanted to log the events. Note that you can customize this message using the information of the parallel.
Test the trigger and confirm that the message is delivered.
If needed, you can also update the HubSpot deal stage to move it to the next stage of your funnel automatically.
Now you can save your Zap and publish to start logging your Parallel events on your Hubspot Deals!
Note: If the parallel doesn’t contain the dealId, the user must add it manually. We recommend always using the “Create a parallel when the stage deal is updated in Hubspot“ integration to automate the dealId association. |