Object - Pick
Type identifier:
object:pickCategory: Object Operations
Description
Extracts specific properties from an object or Record. Creates individual output handles for each selected property, allowing you to access nested fields without using expressions. Automatically adapts output handles based on the connected object's Schema.
Input Handles
Handle | Data Type | Required | Description |
|---|---|---|---|
|
| Yes | The object to extract values from |
Input Handle Details
object
- Type:
objector Record Notes:
- Supports plain objects, Schema-based Records, and arrays
- The connected source determines available pickable properties
Output Handles
Handle | Data Type | Description |
|---|---|---|
| Varies | One handle per selected property |
Output Handle Details
Property Handles
Output handles are dynamically generated based on selectedProperties:
- Handle ID: Dot-notation path to the property (for example,
name,address.city) - Type: Inferred from the source object's Schema
Notes:
- Handles are created for each selected property
- Only connected output handles are evaluated
- File entries are augmented with Record context or Flow run context
- Content types (images, videos, files) receive appropriate context metadata
Configuration Options
Property | Type | Required | Default | Description |
|---|---|---|---|---|
|
| Yes |
| Display label for the node |
|
| Yes |
| Paths to properties to extract |
Configuration Details
selectedProperties
- Type:
string[][](array of path arrays) - Format: Each inner array represents a path (for example,
["address", "city"]foraddress.city) Notes:
- Paths follow Schema property structure
- Only selected properties create output handles
- Invalid paths are pruned when the source Schema changes
Behaviour
Value Traits in Flows v2
Each picked output retains traits on the selected field, its ancestors, and its nested fields. A sensitive sibling does not mark an unrelated picked field. If the entire input object is sensitive, every picked output remains sensitive.
Run inspection shows observed Sensitive traits and nested paths without revealing the containing payload. An unmarked public sibling can be returned through Flow Result. A sensitive output may be returned to an inline child Flow's caller, but not as the top-level Flow run result.
Execution Flow
- Resolves the
objectinput handle - Validates object is not null or undefined
- For each connected output handle:
- Extracts the value at the specified path
- Augments file entries with context (Record or run)
- Augments content nodes (images, videos, etc.) with context
- Produces the requested output values
Property Selection UI
The node provides an interactive property selector:
- Schema properties are listed from connected source
- User toggles checkboxes to select/deselect properties
- Output handles update dynamically
- Orphaned edges are pruned when the Schema changes
Context Augmentation
File and content values receive additional context:
Source Type | Added Context |
|---|---|
Existing Record |
|
New Record (from a Flow) |
|
File with existing context | No changes |
Error Handling
Scenario | Behaviour |
|---|---|
Object is undefined | Throws error |
Object is null | Throws error |
Object is not an object | Throws error |
Property path not found | Returns |
Examples
Basic Property Extraction
{
"type": "object:pick",
"data": {
"label": "Object - Pick - User",
"selectedProperties": [["name"], ["email"], ["address", "city"]]
}
}Creates output handles: name, email, address.city
Picking From Object - Query Results
{
"type": "object:pick",
"data": {
"label": "Object - Pick - Order",
"selectedProperties": [["id"], ["total"], ["items"], ["customer", "name"]]
}
}When connected to an Object - Query result, extracts specific fields from the queried Record.
Extracting File Properties
{
"type": "object:pick",
"data": {
"label": "Extract Document",
"selectedProperties": [["document"], ["uploadedAt"]]
}
}File values are automatically augmented with context for proper resolution.