I'd be happy to connect with you on LinkedIn. Connect with me here: https://www.linkedin.com/in/bradfordcarlton/

This is such an important question — and I think you're right to frame it as a balancing act rather than a simple "yes" or "no." From my wife's experience, AI has been a massive accelerator for agency operations, especially when it comes to tasks like content repurposing and daily internal workflows. It’s allowed her to move faster, experiment more, and stay ahead without needing to immediately expand headcount. That said, I completely agree that the real magic of agency work still lies in human connection — strategy sessions, client relationships, creative insights. In her case, she's treated AI less like a "replacement" and more like an "amplifier." It handles the repetitive, data-heavy work so her team can double down on being human where it matters most. To your question about systems: ✅ She's automated some client onboarding, personalized initial outreach sequences, first-draft content generation, and some internal reporting. ✅ Biggest difference-makers have been AI-powered research assistants and product feed automation tools — it’s freed up an incredible amount of her time without sacrificing quality. Curious — have you found any specific area yet where AI felt like it crossed the line too much and lost that personal touch? I’d love to hear your take!

You'll need to set the field either before or after depending on when it is needed to be set (before if you need your parser to receive the data in a specific way, or after if the output needs to be formatted for further nodes). Think of the "structured output parser" as a tool or model, not an actual node.

Is it the email agent that is causing the issue? You need to set a "response" to send back to the AI agent. Tough to say without some more detail of what worked and what didn't. If it is the Vector Store causing your issues, I'd recommend checking out @Nate Herk 's videos on setting up RAG as he walks through all of the settings that might trip you up.

@Ramon Tomzer Thank you. I went back in and tried to refine it and found a solution.

UPDATE: I found a solution with these settings: Method: Get URL: https://api.search.brave.com/res/v1/web/search Authentication: None Send Query Parameters: On Query Parameters: - Name: q - Value Provided: By Model (and is required) Send Headers: On - Name: X-Subscription-Token - Value Provided: Using Field Below - Value: [API Key] - Name: Accept - Value Provided: Using Field Below - Value: application/json - Name: Accept-Encoding - Value Provided: Using Field Below - Value: gzip Once I had all that set, it worked like a charm. tl;dr: Don't use an authentication method, simply pass the API key through a Header