Inject Data (obsolete)
Audience:
Low-code EngineersSkill Prerequisites:
Actions,Tokens
Adds tokens to the current execution. Each row has a Name and a Value. The value can mix text and tokens, and it's evaluated once when the action runs. Later actions can use the result, for example [FullName].
This action is obsolete. Use Create/Update Tokens instead. Existing Inject Data actions still work, but new applications shouldn't use it. See Migrating to Create/Update Tokens.
Typical Use Cases
- Understand or maintain an existing application that already uses it
- Migrate an existing action to Create/Update Tokens
Don't use it to
- Build anything new. Use Create/Update Tokens, which lets you reorder rows, replace tokens more than once and use tokens in names.
- Keep data for a later request, such as the next submit. Tokens only exist for the current execution.
Related Actions
| Action Name | Description |
|---|---|
| Create/Update Tokens | The replacement. Sets one or more tokens from expressions. |
| Execute Token (Obsolete) | Another obsolete action replaced by Create/Update Tokens. |
| Run SQL Query | Runs SQL and saves the result in tokens. |
Input Parameter Reference
| Parameter | Description | Supports Tokens | Default | Required |
|---|---|---|---|---|
| Data | A list of rows, each with a Name and a Value. The value is the expression to evaluate, for example [FirstName] [LastName]. Tokens in the value are replaced once. Rows with an empty name are skipped. | Yes (Value) | empty list | No |
Output Parameters Reference
| Parameter | Description |
|---|---|
| Data (Name) | Each row's Name becomes a token that holds the evaluated Value. Use it as [Name] in later actions. |
Considerations
- Existing tokens are overwritten. If a token with the same name already exists, its value is replaced. Names aren't case-sensitive.
- Each name is used once. If two rows have the same name, only the lower row's value is used.
- Rows can't be reordered. Create/Update Tokens has ordering, so you can control which row runs first.
- Tokens are replaced once. If the result contains more tokens, they stay as text.
- Type the name without brackets. Enter
FullName, not[FullName]. Tokens in names aren't replaced.
Migrating to Create/Update Tokens
Replace each Inject Data action with a Create/Update Tokens action:
| Inject Data | Create/Update Tokens |
|---|---|
| Data, Name | Token Name of a row in Tokens |
| Data, Value | Token Value of the same row |
| (tokens replaced once) | Number of Recursions set to 1 (the default) |
| (no tokens in names) | Tokenize Token Names unchecked (the default) |
Examples
To understand how to use the below examples, please see Running Examples.
1. Set a full name and a default status (obsolete)
This action sets [FullName] from two tokens and sets [Status] to New.
{
"Title": "Inject Data (obsolete)",
"ActionType": "InjectData",
"Description": "Set the full name and the default status",
"Parameters": {
"Data": [
{
"name": "FullName",
"value": "[FirstName] [LastName]"
},
{
"name": "Status",
"value": "New"
}
]
}
}
2. The same action with Create/Update Tokens
This is the recommended replacement for example 1. It gives the same results.
{
"Title": "Create/Update Tokens",
"ActionType": "ApplyTokens",
"Description": "Set the full name and the default status",
"Parameters": {
"Tokens": [
{
"name": "FullName",
"value": "[FirstName] [LastName]"
},
{
"name": "Status",
"value": "New"
}
],
"RecursionCount": "1"
}
}
Revised 09/26/2026