How variables work
When you type{{variable_name}} anywhere in a prompt message, Adaline automatically detects it and creates a corresponding entry in the Variable Editor panel. You can then set values for each variable before running the prompt in the Playground.

Variable name constraints
Variable names must follow specific rules to ensure compatibility across the platform: Allowed characters:- Letters:
a-zandA-Z - Numbers:
0-9 - Underscores:
_ - Hyphens:
-
| Valid | Invalid |
|---|---|
{{user_question}} | {{user question}} (spaces) |
{{product_name}} | {{user.question}} (period) |
{{user-id}} | {{user@name}} (special characters) |
{{item_123}} | {{user/name}} (slash) |
Variable types
Adaline supports three types of variables, each suited to a different content modality:Text variables
The most common variable type. Define them directly in your prompt text using the{{variable_name}} syntax.
Without variables:

Image variables
Image variables let you dynamically swap visual inputs without changing the prompt structure. To create one:- Click the image button in a message block.
- Select From Variable and give it a descriptive name.
- In the Variable Editor, attach the actual image (URL, base64, or file upload).
PDF variables
PDF variables work the same way as image variables but for document inputs. To create one:- Click the PDF button in a message block.
- Select From Variable and give it a descriptive name.
- In the Variable Editor, attach the actual PDF (URL, base64, or file upload).
Variable sources
Variables can be powered by different sources depending on your workflow needs:
| Source | Description | Use case |
|---|---|---|
| Static | Direct text, image, or PDF content set manually in the Variable Editor. | Simple testing with fixed inputs. |
| API | Fetches live data from external HTTP endpoints at runtime. | Injecting real-time data like user profiles, product catalogs, or live metrics. |
| Prompt | Executes another prompt and uses its output as the variable value. | Building agent-like workflows with prompt chaining. |
Create a variable
Add a
{{variable_name}} placeholder in your prompt text, or create an image/PDF variable through the respective buttons.- API Variables — Fetch live data from external endpoints.
- Prompt Variables — Chain prompts together for complex workflows.
Dynamic sources in datasets
When your variable uses an API or Prompt source and you have a linked dataset, the dynamic source is executed for each row individually. This means:- API variables make a unique HTTP request per row, with placeholders like
{{userId}}resolved from that row’s data. - Prompt variables execute the referenced prompt once per row, passing the row’s context.
- Results are stored in the dataset cells and can be used for subsequent evaluations.

Best practices
- Use descriptive names — Choose names like
{{user_purchase_history}}instead of{{var1}}so that team members can understand the prompt at a glance. - Keep variables focused — Each variable should represent one piece of data. Avoid packing multiple values into a single variable.
- Test with linked datasets — Connect a dataset to your variables to efficiently test across many different input combinations.
Next steps
Use APIs in Prompts
Fetch live data from external endpoints at runtime.
Use Other Prompts in Prompts
Chain prompts together for complex workflows.