Data is at the core of every Flowmage flow.

Understanding how data works will help you build powerful automations—and prevent most common issues.

What are Variables?

A variable is a piece of data that your flow can use.

This can be anything, such as:

• A name

• An email address

• An invoice number

• A status value

Variables are created automatically when your flow receives or processes data.

Accessing Variables in Flowmage

In Flowmage, you can access variables using this syntax:

@nodeName.fieldName@

Example

If you have a GET node named invoice, you can access its data like this:

@invoice.invoiceNumber@

This means:

• invoice → the node name

• invoiceNumber → the field inside that node’s data

? Tip: Always give your nodes clear names so your variables stay readable.

Using Data from Triggers

Most flows start with a trigger, and this is usually where your data comes from.

For example:

• A webhook receives JSON data

• A scheduler might generate timestamps

• A manual trigger might include test data

This data becomes available as variables immediately after the trigger runs.

Example (Webhook Input)

{
  "name": "John",
  "email": "john@example.com"
}

You could access this like:

@webhook.name@
@webhook.email@

Passing Data Between Steps

As your flow runs, each step (node) can:

• Use existing data

• Modify data

• Generate new data

This data is then available for the next steps.

Example Flow

1. Trigger receives data

2. Action (API call) returns additional data

3. Condition checks values

4. Next action uses combined data

Practical Example

• Webhook receives a lead

• API call enriches the lead

• You use both datasets in the next step

@webhook.email@
@enrichment.companyName@

Common Data Mistakes (and How to Avoid Them)

This is where most issues happen. Here are the most common pitfalls:

❌ Wrong Node Name

If your node is called invoiceData but you use:

@invoice.invoiceNumber@

It won’t work.

✅ Fix: Always match the exact node name

@invoiceData.invoiceNumber@

❌ Field Does Not Exist

If the data doesn’t contain a field, it will return empty or fail.

✅ Fix: Check your data structure in logs or test runs

❌ Using Data Before It Exists

You can only use data from:

• Previous steps

• Not future steps

✅ Fix: Make sure the node runs before you reference it

❌ Incorrect Data Format

Sometimes APIs expect:

• Strings instead of numbers

• Specific formats (dates, JSON, etc.)

✅ Fix: Use transformation steps if needed

❌ Typos in Variables

Even small mistakes break things:

@invoice.invoicenumber@ ❌
@invoice.invoiceNumber@ ✅

Best Practices

• Use clear node names (e.g. invoice, leadData, userProfile)

• Test your flow with real data

• Check logs when something doesn’t work

• Keep your data structure simple where possible

Summary

• Variables store the data in your flow

• You access them using @node.field@

• Data flows from step to step

• Most issues come from naming or structure mistakes

Once you understand how data works, Flowmage becomes much more powerful and flexible.