Last week, we introduced all the different nodes with a very basic and short explanation. This week, we will start going over the different nodes in more detail to properly explain how to use these nodes.
The Match node is one of the most important nodes to start with. This node makes it possible for the Workflow to try and find matching records in the Organizations, Persons, and Card Bin databases for use in the rest of the Workflow.
Because of this importance, we suggest that you start with the first node being the Match node, which will make your Workflow look like this:
Now, you will notice that the Match node is currently colored an urgent red and animated (not shown in the image above). This means that the node currently requires some attention, as settings have not been completed. It is important to pay attention to this, as you will not be allowed to save any changes you made to the Workflow until this is attended to.
When you hover over the icon, a pencil button will show up. Clicking on this pencil will open the following window:
As you can see, some fields need to be filled out for the Match node to work. The Lead and Match fields are dropdown fields, which, when you look at them, will contain the relevant Workflow Variables that we defined in the previous blog post.
What is important to note is that the fields will only accept Workflow Variables of the correct type. This means that in the ‘Lead’ field, we will currently only be able to insert the Webform_Data variable, which means the Match node is going to attempt to match the data in the Webform_Data Workflow Variable to the other tables in the database.
For the ‘Match’ field, we will need to create a new Workflow Variable of the ‘Match result’ type. This is the variable that is going to contain the relevant data of any matched records in the other tables. For this post, it will look like this:
Having completed that, we can now complete the variables part of the Match Node, which can now look like this:
The ‘When not matched’ header allows you to select what kind of behavior is expected when the Match node fails to find a matching record:
- Do nothing does, as it very much suggests, nothing. This will mean that there won’t be any available data in the Match variable, which may cause issues further down the line of the Workflow. This should be considered with a branching Condition node that checks for data in the Match variable;
- Add to card catalog will create a new card catalog record, with which the further automation can be continued;
- Add lead when valid Chamber of Commerce will check whether the data found contains a valid Chamber of Commerce id. If one is found, it will create a new Organization and, if possible, Person record with which the automation can be continued;
- Create new lead (Person only) will create a new person lead for use in the automation, but will not take any Organization information in account;
- Create new lead will create both new Organization and Person records if enough data can be found for use in the automation.
Finally, the lines under ‘Minimum score’ allow you to set how much a record should match the data in the Lead variable in order to be considered a ‘match’ and in order to be used in the rest of the automation. The score can range anywhere between 0 and 100, with a score of 100 meaning a perfect match.
If the score of the match meets or exceeds the minimum score, it will be considered a match and put into the Match Variable.
Next week, we will continue with the explanation of the different nodes, concentrating on the Condition node.