Zuper <>HubSpot workflow automation

Zuper <>HubSpot workflow automation

With the HubSpot – Zuper Integration, currently you can create a job in Zuper from HubSpot using the Zuper widget on the right-side pane. This provides flexibility in creating a job to suit your different needs. You can specify the job details in the form and create a job. But this will involve some manual effort.  

HubSpot Workflow Automation allows you to set up the automatic creation of jobs from deals and tickets from HubSpot to Zuper. You will have greater control over when data from HubSpot is pushed using triggers and how the data is pushed to Zuper with the mapping table. You can push a deal or a ticket to a job as well as sync customers and organizations data.  

Pre-requisites: 

 Hubspot Plans – Professional or Enterprise.
 Hubspot Integration installed.  


How to install and use Zuper - HubSpot integration


Install HubSpot


1. Log in to your “HubSpot” account and go to the app marketplace.

2. From the app marketplace, navigate to Customer Service, then Field Service Management, and select "Zuper."

Click here to know more about HubSpot installation. 

Data Flow: 

With workflow automation, we can define how data flows between Hubspot and Zuper. Currently, Data flows from the following Hubspot to Zuper modules are supported: 
  1. Deal to Job 
  2. Ticket to Job 
  3. Contact to Customer 
  4. Company to Organization 
Module-level data flow is predefined and cannot be changed i.e. data from deal will always flow into Job and vice versa.  

Within each module, the fields are mapped which can be controlled by you in the mapping table as explained in the following section. Flows can be unidirectional or bidirectional.  

Field Pairing

In the integration between Zuper and HubSpot, field pairing  is the method used to specify how the fields in Hubspot are connected to the fields in Zuper. This process guarantees that data is accurately moved and interpreted between the two systems.

1. Map the "Deal to Job" fields. HubSpot's fields gets sync with Zuper field.
a. Deals field in HubSpot will get synced with Job fields in Zuper.
b. Contacts field in HubSpot will get synced with Customer fields in Zuper.
c. Company fields in HubSpot get synced with Organization fields in Zuper. 

You can use any one of the arrows to define the way the sync should happen.
i) Single forward and backward arrow represents one way sync. 
ii) Two parallel arrows represents two way sync. 
                 
                                
Note: Click the "Add Field" button to add the additional fields for mapping. 
Note: The default value can be added based on the need or can be kept blank. 


2. Map the "Ticket to Job" fields. HubSpot's fields gets sync with Zuper field.

Click the "Save Changes" button to save & configure the workflow. 



Field Pairing should be specified for all modules which need to be synced between Hubspot and Zuper. Each HubSpot field can be mapped to one Zuper field.  
                                                        

Setup automated workflow

After field mapping is done, you can now set up the workflow to perform the action in an automated process. Trigger workflow in HubSpot and you can see the action in Zuper. 

1. Select the deal based or ticked based blank workflow. 




2. The initial step is enrollment. 

 

3. You can set up the conditions for the trigger to happen. 



4. The event is successfully selected. 


5. Here the relevant Zuper action will be available and can be set here.


6. The deal from HubSpot will be pushed as Job in Zuper. Click the "Review and publish" button. 



7. You can review the configurations set and turn on the workflow. 



The automation has now been set up and is live. Once a Deal/Ticket meets the configured trigger criteria, the object data will be pushed to a Zuper job as per the field mapping specified. The fields will also be kept in sync as per the sync direction specified.

For data flow to happen between other modules, relevant workflows need to be set up. For eg. For data to flow between Ticket to Job, a ticket-based workflow needs to be set up with the relevant Zuper action.  

Important Points: 
  1. It is recommended that only one workflow be set up for each Zuper module sync. i.e. When moving data from a deal to a job, only one deal-based workflow using a Zuper action should be created. 
  1. For Certain Fields, for e.g. calculated fields, the direction of sync can be only unidirectional where they are the source field.    

    • Related Articles

    • How to integrate HubSpot ServiceHub and HubSpot Sales with Zuper?

      With Zuper’s first-class integration with HubSpot ServiceHub, and HubSpot Sales, work seamlessly across your sales, services, and support teams to deliver an exceptional customer experience. Using Zuper integration with HubSpot, you can also easily ...
    • How to integrate and use HubSpot Sales with Zuper?

      The HubSpot Sales – Zuper integration helps create a job using Zuper against the various deals present in HubSpot. 1. Visit: app.hubspot.com and log in with your credentials. Then, under the "Sales" tab, select the "Deals" option. 2. Select the sales ...
    • How to integrate and use Clyr with Zuper?

      Introduction: The Zuper-Clyr integration enables you to automate expense management. Track your expenses by adding your credit card details on Clyr. Sync Jobs from Zuper as Projects on Clyr. Associate expenses to Projects on Clyr. Track your expenses ...
    • How to integrate and use CloudTalk with Zuper?

      With our new Zuper-CloudTalk integration, you can connect your CloudTalk account to Zuper and automatically send outbound SMS through your CloudTalk number. The CloudTalk App is a popular phone app based out of the European region and they support ...
    • How to integrate and use Google Calendar with Zuper?

      With our Zuper-Google Calendar integration, the user can install the Google Calendar from our Zuper store. Then, post-installation, whenever the jobs are created and scheduled for a particular date, this vital job information will be created and ...