Overview
"Other Actions" are built-in, third party webhooks included in your paid plan disguised as an action node. These actions have been simplified to make setting them up easy.
These actions will most commonly need three actions to be useful.
1. Objective to collect the variable for the action to use.
2. The Action itself
3. An Action to do something with the returned variable from the "Other Action"
Example
Example: Our company has a service area of 50 miles. We want to disqualify leads that are outside of the service area and book the leads that are within the service area.
For this example we will gather the contact's address, use a Check Distance action to get the distance between two locations (our office and the contact's home) and then use a True/False action to separate people who are within the service area and outside the service area.
First we will set up the action to get the contact's address. We can bring in an objective and choose the full address options from the Output Variable field. The Action will look like this.
Now that we have the address, we can grab the contact's address variable and enter the address of the business in the Check Distance action.
We have a couple options for which variable we can insert into the field for this.
Contact - Contact.Full Address - This is the most reliable option as it will take a known address from a field in your CRM and that same field will be updated by the Get Full Address action.
Node - Get Full Address.Result - This option is great if your Source is a webhook and you do not have access to fields that hold an address in a CRM. We will use the result of our Get Full Address action to populate the contact's address.
Variables are found by clicking on the "+" icon inside of an action field.
For this example we will add the Contact.Full Address variable into the Destination field of the Check Distance action.
In the Origin field we can type in the business's address or we can choose the variable Location.Address (a great option if you have multiple sources using the same Job Flow).
We will add the address of the business in the Origin field.
Finally, we will set up our True/False action to be able to utilize the data that we received from the tool.
While using the True/False in this way, we do NOT use AI to Power the Decision because we are working off of variables and not the conversation.
The results from the Check Distance Action will be available as a Node variable. It will display as the Title of the Check Distance action. From here we will be able to use which ever variable we want that was returned.
We will put this Check Distance.DistanceMiles in the Left Value field.
The Operator will be LessThanEqual.
The Right Value will be the max distance that our company is willing to travel.
The action is set up to see if the distance between our company and the contact's address (represented by Check Distance.DistanceMiles) is Less Than or Equal to the maximum allowed distance (the Right Value).
If the contact meets the above condition, it will go down the true branch. If they do not meet the condition, they will go down the false branch.