Jump to Another Action Tool

There are several scenarios where, within your automation, it may be necessary to ensure that, when the flow reaches a certain step, other steps should be ignored or jumped over.

Using the Jump to Another Action tool, you can configure this type of flow in just a few steps. This will allow you to create even more precise automations that can handle different circumstances.

Below, you can see a practical example of how this tool can be used.

How to jump to another action if a specific value is not found

Imagine a scenario where we want to create a deal in Pipedrive for new orders received in Ecwid. In this scenario, before creating the deal, we need to check whether a contact (person) for that customer already exists in Pipedrive.

The contact search in Pipedrive can be performed using different values, such as a phone number or an email address. However, there may be scenarios where the Ecwid buyer does not provide one of these two values.

Let’s see, in practice, how to handle this situation, ensuring that a deal is always created and associated with the correct person.

The first step will be to add the Ecwid New Order trigger to your automation:

Attention: In this example, we are using the Ecwid app to send data to Pipedrive, but you can apply the same logic to collect and send data to other apps where similar scenarios may occur.

Next, let’s add all the steps we will need.

Don’t worry, we can fill them in later. The idea here is to first create the structure of the automation.

In this case, we will add, in this order, the Find Person by Phone, Find Person by Email, Create Person, and Create Deal steps.

It will look like this:

Now, let’s add the Router steps.

Click here to add a tool:

Select the Router:

Configure the Router so that, if the phone field is filled in, the flow goes to the step that searches for the contact by phone.

Otherwise, it should go to the step that searches for the contact by email.

The configuration will look like this:

Since there is a possibility that the contact may not be found either by email or by phone, meaning that they do not yet exist in Pipedrive, we will configure an error handler for these search steps.

Click here to add the error handler:

Configure it so that, if an error occurs, the automation jumps to the Create Person step.

Repeat exactly the same process, but this time in the action that searches for a person by email.

Now, we will have a flow that knows exactly when to search for a contact by phone, by email, and what to do when that person is not found in Pipedrive.

The final step will be to add the Jump to Another Action actions.

These steps will ensure that the flow follows the correct order when contacts are found. In other words, as soon as they are found, the automation should jump to the Create Deal step.

Simply add this action after the contact search by email and after the contact search by phone, as follows:

Then, within them, configure both in the same way, redirecting the automation to the Create Deal step.

Finally, you just need to fill in the fields in all the steps.

In the step that searches for a contact by phone, use the phone field as the search value:

Repeat the same logic in the action that searches by email:

In the Create Person action, you can add any data from the trigger that you want, for example:

Finally, in the Create Deal action, you should use whichever fields you want to customize the deal. However, in the Person ID field, add the three possible values we may have: the ID found in the phone search step, the ID found in the email search step, and the ID returned when creating the person.

Don’t worry, since only one of these fields will contain a value in each execution, we will only send the correct ID.

Finally, simply activate the automation, and you will have a customized flow that covers several possibilities, ensuring that your order data is correctly collected and sent to your CRM, with no room for errors.

Related articles

• How to Use Error Handler in Your Automations