Skip to main content
Automations are currently in beta. Features and behavior may change.
Automations move data between nodes with expressions. Wrap a path in double braces and Wanhap replaces it at run time with the real value:
Expressions work in any text field of any node — prompts, webhook payloads, HTTP bodies, condition fields, and more.

​
What data is in scope

This is the rule that trips people up most:
A node can only use data from nodes connected before it (upstream). If a node isn’t on the path leading into the current node, its data isn’t available.
So a Generate node placed after a Fetch RSS node can use {{ fetched.title }}, but a node that runs before the fetch cannot — the data doesn’t exist yet at that point in the flow.
In any field, type {{ to open an autocomplete of exactly what’s in scope at that node. Known references are highlighted; unknown ones are flagged so you catch typos before running.

​
Expression reference

Which expressions exist depends on which nodes run upstream.

​
Schedule trigger

Available when the flow starts from a Schedule trigger.

​
Post trigger

Available when the flow starts from a Post published or Post scheduled trigger.

​
Fetch RSS

Available downstream of a Fetch RSS node.

​
HTTP Request

Available downstream of an HTTP Request node. The whole JSON response is exposed as fetched, so you append whatever path you need:

​
Generate

Available downstream of a Generate node.

​
Always available

These work anywhere in any flow.

​
Workflow variables

Workflow variables are reusable values you define once and reference anywhere with {{ variables.KEY }}. They’re scoped to a single automation. Use them for values you repeat across nodes or want to keep out of node fields — API keys, base URLs, account handles, a default hashtag.
1

Open the Variables tab

In the Workflow editor, switch to the Variables tab in the right sidebar.
2

Add a variable

Give it a key (letters, numbers, and underscores — e.g. API_KEY) and a value.
3

Reference it

Use {{ variables.API_KEY }} in any field, in any node.
Variable values are stored encrypted. They’re safe for secrets like API keys.

​
See it in action

The surest way to learn what’s available is to run the flow:
Click Run test in the editor and open the result panel. Each node shows its exact input and output, so you can see precisely what every expression resolves to. See Testing and monitoring.