Step Outputs & Variables

Automation actions often need dynamic values—the lead's email, a field from a previous step, or formatted data. Leadflip supports variables that you can insert into action configurations. Variables are resolved at runtime with the actual lead data and step outputs.

Leadflip provides a built-in variable editor in every action that supports dynamic values. Instead of typing variable syntax manually, you can click the variable button next to input fields to open a dropdown of all available lead fields and previous step outputs. Simply select the variable you want and it will be inserted at the cursor position.

Variable Syntax

Variables use double curly braces:

{{ variable_name }}

For example, in an Email action's body:

Hi {{ lead.first_name }},

Thanks for submitting the form. We'll reach out soon.

At runtime, {{ lead.first_name }} is replaced with the lead's first name.

Lead Fields

Reference any lead field with the lead. prefix:

Use the exact field slug from your Entity for custom fields. For example, if you have a field "Lead Source" with slug lead_source, use {{ lead.lead_source }}.

Step Outputs

Some actions produce outputs that you can reference in later steps. For example:

• Webhook – May return a response body or status code.
• Format – Produces a formatted value.
• Filter/Path – May expose which branch was taken.

Reference step outputs with the step name or ID:

{{ steps.webhook_1.response.body }}
{{ steps.format_name.output }}

The exact syntax depends on how each action exposes its outputs. Check the action's documentation or tooltip in the builder.

Common Use Cases

• Personalized emails – Hi {{ lead.first_name }}, in the email body.
• Webhook payloads – Send {{ lead.email }} and {{ lead.phone }} in a JSON body.
• Filter conditions – Compare lead.status or lead.source to route leads.
• Update Fields – Set a field to a value from a Format step.

Best Practices

• Handle empty values – If a variable might be empty, consider how the action will behave (e.g., an email with a blank name).
• Use Format for complex logic – When you need to concatenate, parse, or transform data, use a Format action and reference its output.
• Test with real data – Run the automation with a sample lead to verify variables resolve correctly.

Next Steps

• See all available actions
• Use variables in Filter/Path conditions
• Check automation logs to verify variable values