Data to API in Legale: send your CSV data to other systems with rules and alarms

Data to API is the part of Legale CSV automations that takes the data from your CSV file, and from your smart documents, and sends it by callback to another system’s API. With conditional rules you decide which value goes out in each field, and with alarms you can schedule reminders using dates from the same CSV.

Where to configure it

Go to Automation → CSV, open the automation and go to the Data to API section. There you define which fields are sent, the rules that transform their values and the alarm settings. If you don’t have a CSV automation yet, start with the help center guide Set the CSV automation configuration.

Conditional rules per field

Each field you send can have one or more conditions. In each condition you choose:

• Where the value to compare comes from: a smart document (you pick a variable) or the CSV (you pick a field).
• The logical condition to evaluate.
• The comparison value.

With the + button you add as many conditions as you need and join them with connectors: & (and), | (or) and != (not, different). This lets you build rules such as “if the country is Chile and the amount is greater than 1,000”.

The Filled condition checks whether the field or variable contains information before applying the rule. When you choose it, the comparison value field is hidden because it isn’t needed.

Available operators

Conditions accept these operators: =, !=, >, <, >=, <=, contain, not contain, empty and filled.

Output value: transform the data before sending it

The optional Output Value field defines what is sent in the callback when the condition is met. For example, if the CSV column contains the code 320 and the condition is met, you can send “chilena” instead of 320.

• If the condition is met and there is an output value, the output value is sent.
• If the condition isn’t met, the original CSV value is sent.
• If you leave the output value empty, the original value is sent too.
• Only the field with the rule changes; all other CSV fields are sent as they are.

In the rule settings, the value to compare appears before the conditional word, which is free text and optional. The output value exists only in Data to API: it doesn’t appear in workflow conditional rules.

Alarms with manual dates or dates from the CSV

In Data to API you also configure alarms with a title, description, start date and end date. Dates can be set in two ways:

• Manually: choose the start and end dates in the calendar.
• From the CSV: with the “Get date from → CSV” option, the calendar is disabled and you choose which CSV columns hold each date. That way each row can have its own dates.

Dates stay saved when you reopen the configuration, and alarm data is stored in its own columns (alarm_title, alarm_description, alarm_start_date and alarm_end_date), separate from the CSV variables.

How Data to API has changed

• November 2025: multiple conditions per field, connectors and the Filled condition.
• December 2025: output value, more operators, alarms with dates from the CSV and alarms stored in their own columns. That month the output value was also removed from workflow rules, where it appeared by mistake.

Frequently asked questions

What is sent if the condition isn’t met?

The original value from the CSV column.

Can I combine several conditions in the same field?

Yes. Add them with the + button and join them with the and, or and not connectors.

Can an alarm’s dates come from the CSV?

Yes. Choose “Get date from → CSV” and select the column for each date.

To use conditions to decide who signs or who gets notified, see conditional rules in Legale. For integrations with other systems, check the API documentation and the guide Managing external integrations. Questions? Create a ticket from My Tickets or talk to our support team.