Processing Components
Processing components transform, combine, and manipulate data as it flows through your automation. Use them to prepare data for conditions, format content for actions, or extract specific values.Data Object Fundamentals
All data in Agent Studio flows as Data objects - structured key-value containers:Create Data V2
Creates a new Data object with specified key-value pairs.When to Use
- Initialize data at the start of a flow
- Create structured data from multiple sources
- Build payloads for API calls or actions
Configuration
| Field | Description |
|---|---|
| Number of Fields | How many key-value pairs (1-15) |
| Field 1 Key | Name of the first field |
| Field 1 Value | Value (supports @ notation) |
| … | Additional fields as configured |
Example: Build Email Context
Configuration:Update Data V2
Adds or updates fields in an existing Data object.When to Use
- Add computed fields to existing data
- Append metadata or timestamps
- Modify values for downstream processing
Configuration
| Field | Description |
|---|---|
| Number of Fields | How many fields to add/update |
| Field N Key | Field name to add or update |
| Field N Value | New value (supports @ notation) |
Example: Add Timestamp and Flag
Input:Filter Data V2
Creates a new Data object containing only specified keys.When to Use
- Remove sensitive fields before logging
- Reduce data size for downstream processing
- Extract specific fields from complex objects
Configuration
| Field | Description |
|---|---|
| Keys | Comma-separated list of keys to keep |
Example: Keep Only Essential Fields
Input:Extract Key V2
Extracts a single value from a Data object.When to Use
- Get a specific field for a condition
- Extract a value to use as a standalone input
- Access nested values
Configuration
| Field | Description |
|---|---|
| Key | The key to extract (supports dot notation for nested values) |
Example: Extract Nested Value
Input:Combine Data V2
Merges multiple Data objects into one.When to Use
- Combine data from multiple sources
- Merge results from parallel paths
- Aggregate data for reporting
Configuration
| Field | Description |
|---|---|
| Operation | How to combine: Concatenate, Append, Merge, or Join |
| Inputs | Connect multiple data inputs |
Operations Explained
Concatenate
Combines arrays of Data objects into a single array.Append
Adds new Data objects to an existing array.Merge
Combines fields from multiple objects into one (later values override earlier).Join
Combines objects based on a common key.Select Data V2
Selects a single item from a list of Data objects by index.When to Use
- Get the first or last item from a list
- Access a specific item by position
- Extract one result from a query
Configuration
| Field | Description |
|---|---|
| Index | Position to select (0-based, negative values count from end) |
Example: Get First Account
Input:Example: Get Last Item
Configuration:Calculate Expression V2
Evaluates mathematical expressions on data fields.When to Use
- Compute percentages or ratios
- Perform arithmetic operations
- Calculate derived metrics
Configuration
| Field | Description |
|---|---|
| Expression | Mathematical expression (supports @ notation for values) |
| Output Key | Name for the result field |
Supported Operations
| Operation | Syntax | Example |
|---|---|---|
| Addition | + | @a + @b |
| Subtraction | - | @total - @discount |
| Multiplication | * | @price * @quantity |
| Division | / | @score / 100 |
| Modulo | % | @value % 10 |
| Parentheses | () | (@a + @b) * @c |
Example: Calculate Percentage
Input:Current Date V2
Returns the current date and time in a selected timezone.When to Use
- Get the current timestamp for data enrichment
- Compare dates in conditions
- Add timestamps to records or messages
Configuration
| Field | Description |
|---|---|
| Timezone | Select the timezone (default: UTC). Supports all standard timezones. |
Output Data
Date Formatter V2
Automatically formats all date fields found in a Data object to a specified format.When to Use
- Standardize date formats before sending emails or Slack messages
- Convert ISO dates to human-readable formats
- Prepare data for external API calls that require specific date formats
Configuration
| Field | Description |
|---|---|
| Date Format | Target format for all date fields (e.g., %Y-%m-%d, %B %d, %Y) |
How It Works
The component recursively scans all fields in the input Data object (including nested objects), detects ISO date strings, and reformats them to the specified format.Example
Input:Using @ Notation
The@ symbol references values from incoming data:
| Syntax | Description | Example Result |
|---|---|---|
@field | Top-level field | @name → “Acme” |
@field.nested | Nested field | @account.owner.name → “Jane” |
@field[0] | Array index | @contacts[0] → First contact |
@ | Entire data object | Full incoming data |
Dynamic Field References
You can build field references dynamically:priority_level is “high”, creates field alert_high.
Common Patterns
Pattern: Data Enrichment Pipeline
Pattern: Data Filtering Before Action
Pattern: Aggregate Multiple Sources
Pattern: Extract and Validate
Best Practices
Build data incrementally
Build data incrementally
Start with Create Data for essential fields, then use Update Data to add more as needed.
Filter before external calls
Filter before external calls
Remove sensitive or unnecessary fields before sending data to external systems.
Name output keys clearly
Name output keys clearly
Use descriptive key names that indicate the data’s purpose and origin.
Handle missing keys
Handle missing keys
Use conditions to check if required keys exist before processing them.
Next Steps
Logic Components
Add conditional routing
Action Components
Use processed data in actions