Pick Field

What it does: Selects only the data fields you need from complex objects, making your data simpler and workflows faster.

Perfect for: API response filtering • Data privacy • Performance optimization • Focused processing

What It Does

• Select specific fields - Choose exactly which data you want to keep
• Remove sensitive data - Exclude private information before sharing
• Reduce data size - Make workflows faster by processing less data
• Handle nested objects - Access deep data structures easily

How It Works

graph LR
    A[Complex Data] --> B[Pick Field]
    B --> C[Selected Fields Only]

    style A fill:#e1f5fe
    style B fill:#e8f5e8
    style C fill:#f3e5f5

Simple process: Complex data → Pick Field selects what you want → Clean, focused data

Common Field Selections

• Basic Fields: Just pick name, email, and phone.
• Nested Fields: Grab data deep inside an object, like user.profile.email.
• Arrays: Get the title of the first post (posts[0].title) or the rating of every review (reviews[*].rating).
• Exclude Mode: Instead of picking what to keep, you can choose what to remove (like passwords or sensitive IDs).

Real Example

Before (Too Much Data): You get a huge response from an API containing the user’s ID, full address, social security number, admin notes, marketing preferences, and more. Example: {"user": {"ssn": "123", "internal_notes": "VIP", "name": "Alice"...}}

The Selection: You only ask for:

• User’s Name
• Email
• Phone
• Theme Preference

After (Just What You Need): The node discards everything else, leaving you with a clean, safe, and small object:

{
  "user": {
    "name": "Alice Johnson",
    "email": "alice@company.com",
    "phone": "+1987654321"
  },
  "preferences": {
    "theme": "dark"
  }
}

Common Use Cases

API response filtering - Extract only relevant data from large API responses Data privacy - Remove sensitive fields before sharing data externally Performance optimization - Reduce data size to speed up processing Focused processing - Create clean datasets for specific workflow needs

Quick Troubleshooting

Missing field errors: Check field names are spelled correctly and exist in your data Nested fields not working: Use dot notation like “user.profile.name” for nested data Array access issues: Use [0] for first item, [*] for all items in arrays

What’s Next?

Related nodes: Edit Fields • Filter • HTTP Request

Common workflows: Data Processing Patterns • API Integration • Privacy-Safe Workflows

Learn more: Data Transformation Guide • Multi-Step Workflows