Format data in your workflow

Learn how to use the Data Formatter to transform field values as they pass through your workflow, changing text case, extracting specific data, reformatting dates and numbers, and more.

What the Data Formatter does

The Data Formatter lets you apply a transformation rule to a data field before it reaches your action step. Instead of passing a raw value from your trigger directly to your destination app, you can reshape it first.

A few examples of what you can do:

• Capitalize names before writing them to a CRM
• Strip HTML tags from a field that contains formatted text
• Extract just the phone number from a field that contains mixed content
• Reformat a date to match what your destination app expects

Rules are applied per field. You can add as many rules as you need, each targeting a different field.

Before you begin

Before you start, make sure you have:

• A workflow open in the builder with the trigger fully configured and tested
• A successful trigger test run completed so field data is available to select

Steps

1. Open the Test tab on your trigger

In the workflow builder, click the trigger node. In the configuration panel, click the Test tab.

2. Open the Data Formatter

Click the data formatter icon in the Test tab toolbar. The Data Formatter modal opens on the Content Rules tab.

3. Click + Add New Rule

Click the green + Add New Rule button. The Add New Content Rule modal opens.

4. Select a Transform Rule

Click the Transform Rule dropdown and select the transformation you want to apply. When you select a rule, a yellow banner appears below the dropdown with a plain-language description of what it does. Use this to confirm you've chosen the right one.

See the Transform Rule reference at the bottom of this article for the full list of available rules.

5. Select the field to transform

In the Output Item field, click the blue + button. The Choose Data (Output Item) picker opens inline, showing all available fields from your trigger step with orange sample values beside each one.

Click the field you want to transform. It appears as a token in the Output Item field.

6. Save the rule

Click Save. The rule appears as a row in the rules table in the Data Formatter modal, showing the transform rule name, output item, and any additional value if required by the rule.

7. Add more rules if needed

Repeat steps 3–6 for each additional field you want to transform. Each rule targets a separate field.

8. Apply the formatter

Click Apply to save all rules and close the Data Formatter modal.

What to expect next

Formatted values are available to use in your action step's field mapping. When you map fields in the action's Mapping tab, the transformed versions of your trigger fields will appear alongside the originals in the Choose Data picker. Select the formatted version to use the transformed value in your destination app.

Using Lookup Tables

The Lookup Tables tab lets you map specific incoming values to different output values, useful when the value in your trigger app needs to be translated before reaching your destination app.

For example, if your trigger app uses date format 09/26/2025   but your destination app expects 26/09/2025  , a Lookup Table rule handles that translation automatically.

To add a Lookup Table rule:

1. Open the Data Formatter and click the Lookup Tables tab.
2. Click + Add New Rule. The Add New Content Rule modal opens showing the Lookup Table form.
3. In the Output Item field, click the blue + button and select the trigger field whose value you want to translate.
4. In the mapping grid, enter the incoming values in the Lookup column (left) and their corresponding replacement values in the Change to column (right). Click the green + button to add more rows.
5. Optionally, enter a Fallback Value. This is what Conduitly will use if the incoming value doesn't match any row in your lookup table.
6. Click Save, then Apply.