If you want to configure a HubEngine plan to synchronize two systems, you can of course get started right away if you know all the necessary credentials and configurations (triggers, actions, conditions, mapping, etc.). Here you will find step-by-step instructions:
If you can’t get started right away, you can also prepare a plan ahead of time by preparing and defining the content of the most important configurations:
You have several options for how to set up your plan triggers:
If you choose scheduled, you should define the interval beforehand. You configure this via Cron. Here you can configure your interval quickly and easily:
The most common intervals such as every minute, every hour, etc. can be selected in the HubEngine via the user interface. So in which interval should your plan be executed? E.G.
- every minute
- every 15 minutes
- every hour
- every night at 3 am
If you choose a webhook, then you include the synchronization in an existing process that should trigger the plan execution.
It is easier to prepare the field mapping if you have access to the systems you want to synchronize. Because it is most effective if you prepare the field mapping with the actual field names and not its labels. For example, preparing a mapping could look like this:
- first_name : first_name, type = string
- last_name : name, type = string
- e_mail : mail_address, type = string
- gender : salutation, action = (“male” to “Mr”; “female” to “Mrs”), type = string
- profile_score : score, type = int
If you do not have access to one system yet, you can at least gather the fields you want to synchronize from the other system.
Do you need conditions for your synchronization? Meaning, should only certain records be transferred? Like for example should only data records be transferred, which
- have met a certain score
- are flagged for synchronization
- are assigned to a specific region
- have opened an email
You can prepare the conditions even before configuring the plan. However, they depend on your processes.
Do you want to perform an action with the plan execution? Actions mean that you can write a certain value into a field in the receiving plan (output). E.G:
- Set the value “SAP” (if coming from an SAP system)
- Set a specific score
- Activate/deactivate lead contact sync
- Activate checkbox when scoring reaches value x to trigger follow-up processes in target system