3 - Decision Rules
In this step you can program the logic behind the decisions made for each record. The system is basically a list of if-then conditions based of how many records or object are found in the destination data after searching for a specific property/column.
Let's do an example:
Let's say that you are creating a Database -> HubSpot and you have companies store in the following table and want to send this data to HubSpot Companies using the name as key to know if the current company in the database is already present in HubSpot:
| ID | Name | City |
|---|---|---|
1234 | Acme Ltd | Milan |
We can build our decision rule like this:
IF [ Company Name ] = 0: ADD = 1: UPDATE > 1: STOP
This decision rule can be read as: If you search in HubSpot for "Company Name" equals to "Acme Ltd." and you find 0 results, then add the record as new object using the "Database mapping" as translation layer. If you find exactly 1 result, update it. If you find more than 1 results, skip this record and go to the next.
You can concatenate more than one decision rules, they will be evaluated in cascade using the "NEXT" decision to jump from one decision rule to the next one.
The difference between the NEXT and STOP is the following.
Last updated