Table replacement: Convert Values Between Apps

The Table replacement tool lets you replace one value with another before passing data to the next step of your automation.

This is useful when different apps use different formats to store the same information. For example, one app may send a text value, while another expects a numeric ID.

A common use case is transferring data between RD Station and Pipedrive:

• RD Station stores multiple-choice field values as text.
• Pipedrive stores the same options as numeric IDs.

To send data correctly between these apps, you need to convert the text value into the corresponding ID. The Table replacement tool allows you to automate this conversion.

How it works

In this example, we'll create an automation that:

• receives a lead from RD Station using the Lead Marked as Opportunity trigger;
• creates a deal in Pipedrive using the Create Deal action.

The trigger sends the value: Above R$ 1 million.

However, the corresponding option in Pipedrive is stored as 48.

If Pipedrive receives the text value instead of the ID, the field may not be populated correctly. To avoid this, we can use Table replacement to convert the value before sending it to Pipedrive.

This example uses RD Station and Pipedrive, but the same approach can be applied to any apps where values need to be converted from one format to another.

Step 1. Add the tool

Add the Table replacement tool after the trigger.

Select Table replacement from the list of available tools.

Step 2. Configure replacement rules

Choose the field that contains the value you want to convert.

In our example, this is the Company Revenue field received from RD Station.

The trigger returns the value: Above R$ 1 million.

Next, identify the corresponding option in Pipedrive and find its ID.

In this example, the option ID is: 48.

Now create a replacement rule:

Incoming value	Replacement value
Above R$ 1 million	48

Whenever the trigger receives Above R$ 1 million, the tool will return 48.

Repeat this process for every available option in the field.

For example:

Incoming value	Replacement value
Up to R$ 100,000	45
R$ 100,000 – R$ 500,000	46
R$ 500,000 – R$ 1 million	47
Above R$ 1 million	48

Step 3. Set a default value

The Default value is used when the incoming data does not match any configured rule.

For example, if a new option appears in RD Station and no replacement rule exists for it, the tool will return the default value instead.

Choose an ID that makes sense for your workflow, such as an "Other" or "Unknown" option if one is available.

Step 4. Use the result in the action

Open the Create Deal action in Pipedrive.

Locate the multiple-choice field you want to populate and map the Result field from the Table replacement tool.

Instead of sending the original text value, Albato will send the ID returned by the tool.

As a result, Pipedrive will correctly recognize and save the selected option.

Reverse conversion

The same logic can be used in the opposite direction.

For example, Pipedrive may send a numeric ID while RD Station expects a text value. In this case, configure the replacement rules in reverse:

Incoming value	Replacement value
48	Above R$ 1 million

When the automation runs, Albato will convert the ID into the corresponding text value before sending it to RD Station.

Use cases

The Table replacement tool can be used whenever values need to be standardized between apps, including:

• converting text values into IDs;
• converting IDs into text values;
• mapping statuses between different systems;
• standardizing lead sources;
• transforming categories, tags, or custom field values;
• ensuring data compatibility between apps that use different formats.

By configuring replacement rules once, you can ensure that data is transferred correctly between systems without manual adjustments.

Now you can convert values between apps with Table replacement. If you have any questions, contact our support via chat.