Welcome to Albato Help

How to Find a Contact ID in Application Steps Where This Field Is Required


IN THIS ARTICLE

If you use Apollo steps in Albato, some actions may ask for a Contact ID. This usually happens when the step needs to work with a contact record, for example when you add a contact to a sequence, link a deal, or run another contact-related action.

Each app has its own internal Contact ID. A Contact ID from one app will not work in another, so this field must always be filled with a value that comes from the same app as the action.

In this example, we will use Apollo and the Add a Contact to a Sequence action. A Contact ID may look like this: 359494/374028.

 

What Is a Contact ID

The Contact ID is a unique internal value in each application. This means the Contact ID used in Apollo is different from the Contact ID used in any other app.

For example, when you fill in the Contact ID field in the Add a Contact to a Sequence action in Apollo, the ID must belong to a contact in Apollo. If you use a Contact ID from another app, the step will return an error.

There are three common ways to fill in this field.

 

1. Use a Fixed Value

This option is less common, but it works when the same lead should always be added to the sequence after the trigger runs.

In that case, you can enter the Contact ID manually in the field.

Enter a fixed Contact ID in Apollo

This ID was copied directly from Apollo. Each app has its own way to display a contact ID, so if you are not sure where to find it, check the app documentation or contact the app support team.

Please, note: In this setup, the same lead will always be used in the action. The trigger data will not change which contact is added to the sequence.

 

2. Find the Contact ID

In most cases, the best option is to find the contact first. Many apps include a contact search step that lets you search by email, name, or phone number received from the trigger.

In Apollo, add a new action before Add a Contact to a Sequence.

Add a new action before the Apollo sequence step

Select Apollo and choose Find Contact.

Select the Find Contact step in Apollo

Choose which value you want to use for the search. In this example, the trigger provides an email address, so we will use that value.

Use the email value to search for the contact

After that, go back to Add a Contact to a Sequence. The search step will provide the Contact ID value you need.

Open the step where the Contact ID is required

In the Contact ID field, select the value returned by Find Contact.

Map the Contact ID from the Find Contact step

Please, note: This option works only if the contact already exists in Apollo. If the contact is not found, no Contact ID will be returned, and the next steps may fail.

 

3. Create a Contact

If you want to make sure a Contact ID is always available, create the contact before the step that requires it.

Add a new action before Add a Contact to a Sequence.

Add a new action before the sequence step

Select the Create Contact action in Apollo.

Select the Create Contact action in Apollo

Fill in the available fields with values from the trigger so the new contact is created with the right data.

Fill in the Create Contact step with trigger data

Then open Add a Contact to a Sequence.

Open the sequence step after creating the contact

In the Contact ID field, use the value returned by Create Contact.

Use the Contact ID from the Create Contact step

 

How to Handle Both Scenarios in One Automation

If you are not sure whether the contact already exists in Apollo, you can build the automation so it handles both cases.

Start by adding Find Contact.

Add the Find Contact step

Then click the plus icon to add a tool.

Add a tool after the contact search step

Select Branching.

Select the Branching tool

This lets you create one path for contacts that do not exist yet and another path for contacts that are already in Apollo.

Open the first branch.

Open the first branch for configuration

Configure the condition so this branch runs only when the Contact ID from Find Contact is empty. This means Apollo did not find an existing contact.

Set the condition for an empty Contact ID

In this branch, add Create Contact.

Add the Create Contact step in the first branch

Fill in the step with the same contact data used earlier.

Fill in the Create Contact step in the first branch

Then add Add a Contact to a Sequence and use the Contact ID returned by Create Contact.

Open the sequence step in the first branch

Map the Contact ID from the Create Contact step

Now configure the second branch for the case where the contact already exists.

Click to add another branch.

Add the second branch

Set the condition so the Contact ID from Find Contact contains a value.

Set the condition for a Contact ID with a value

In this branch, add Add a Contact to a Sequence.

Add the sequence step in the second branch

In the Contact ID field, use the value returned by Find Contact.

Now you can use the correct Contact ID in Apollo steps and avoid errors in your automation. If you have any questions, contact our support via chat in your Albato account.

Did this answer your question?