ChatGPTSalesOutreachAI score · 74/100AI-assisted edit · no obvious prompt-injection riskn8n.io

n8n Multi-Agent Cold Email Campaign Generator: O3 Director + GPT-4.1 Specialists

Build a chat-triggered multi-agent workflow in n8n: an O3 Director Agent orchestrates strategy while six GPT-4.1-mini Specialist Agents run research, copywriting, personalization, sequencing, deliverability, and analytics in parallel, then integrate into a complete cold email campaign plan.

Some experienceStepsWorkflowTip
Who
Sales and marketing operators who want to quickly build an AI-powered cold email campaign in n8n and reduce OpenAI costs via agent specialization
You get
Receive a complete cold email campaign plan—including prospect research, email copy, personalization variables, follow-up sequence, deliverability tips, and analytics—by sending a natural-language request via the n8n chat trigger
You need
n8n · chat-trigger · ai-agent · agent-tool · openai

Constraints

Prerequisites: accessible n8n instance (self-hosted or cloud); OpenAI API Key configured in n8n credentials. Input: send a natural-language request via the n8n Chat Trigger (e.g., "Create a cold email campaign for SaaS CTOs"). Output: an integrated campaign plan returned by the Director Agent. Cost: depends on OpenAI API usage; author claims ~90% savings by using O3 only for strategy and GPT-4.1-mini for tasks (unverified).

What they did

Author Yaron Been created an n8n workflow template that simulates a virtual sales and marketing team: after a user sends a request via chat, the Outreach Director Agent (O3) performs strategic planning using the Think tool, then delegates tasks in parallel to six Specialist Agent Tools (GPT-4.1-mini) covering prospect research, cold email copywriting, personalization, sequence strategy, deliverability, and analytics. The Director finally integrates all outputs into a cohesive cold email campaign plan.

How it went

No runtime data or user feedback for this template is provided by the source. The template page shows 3,033 total views (author_report). The author claims ~90% cost savings by using O3 only for strategy and GPT-4.1-mini for tasks; this figure is unverified.

Worth knowing

1) Specialist nodes use an empty template `={{ $fromAI('Prompt__User_Message_', ``, 'string') }}` in the text field; the Director dynamically injects the user message at runtime. This is not a pre-written fixed prompt—if you need to constrain a Specialist's behavior, you must add configuration yourself. 2) The template does not include actual email-sending nodes (e.g., Gmail/SendGrid); it produces a campaign plan as text, and additional integration is needed to execute sends. 3) credential_types in workflow.json is empty, but a valid OpenAI API Key credential is still required to run. 4) Sticky notes contain the author's support contact ([email protected], YouTube, LinkedIn) as operational info, not technical steps. 5) This site has not imported or run the workflow; reproduction=not_tested.

n8n workflow template

Structure checked · Not run-tested

Use “Import from File” in n8n, or copy the JSON and paste it into the editor. Connect your own accounts, then try test data. The template is inactive by default.

Setup and test checklist

Credentials to connect

  • After import, connect your own credentials on auth-required nodes; author secrets are not included.

Configuration to replace

  • Source template is n8n public workflow #6909 (~18 nodes). Keep inactive after import; verify triggers, expressions and external API endpoints.
  • Sticky-note guidance is informational; replace placeholders with your own accounts, sheet schemas or channel IDs.

Test input and expected output

  • Manually run the main path once in a test workspace and confirm credentialed nodes authenticate without errors.
  • Drive one synthetic/redacted sample through and check output fields and downstream writes before enabling in production.

Template changes

  • Author credential bindings, webhookId and execution data are removed; the workflow is inactive. Nodes, connections and original prompts are preserved. Not run-tested in n8n.
  • No business-logic edits; verify keys, quotas and privacy compliance before use.

Template retrieved: 2026-10-24

Steps

  1. Add the Chat Trigger node

    Add a "When chat message received" node (type @n8n/n8n-nodes-langchain.chatTrigger, version 1.1) to the workflow canvas. The default webhookId is outreach-webhook-id; no extra parameters are required to receive user requests through the n8n chat interface. Once saved, the workflow can be triggered from the built-in chat or external messages.

  2. Configure the Outreach Director Agent (O3)

    Add an "Outreach Director Agent" node (type @n8n/n8n-nodes-langchain.agent, version 2.1). Connect its language model to the "OpenAI Chat Model Director" node with model set to o3. The Director parses user requests, formulates campaign strategy, and delegates tasks to downstream Specialist Agent Tools.

  3. Connect the Think tool for the Director

    Add a "Think" node (type @n8n/n8n-nodes-langchain.toolThink, version 1.1). Connect its ai_tool output to the Outreach Director Agent's tool input. The Director can invoke this tool for strategic planning before delegating tasks.

  4. Add and configure the six Specialist Agent Tools

    Add the following six Agent Tool nodes (type @n8n/n8n-nodes-langchain.agentTool, version 2.2), each connecting its ai_tool output to the Outreach Director Agent: 1. Prospect Research Specialist — model via OpenAI Chat Model1 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in prospect research, company analysis, pain point identification, and personalization insights" 2. Cold Email Copywriter — model via OpenAI Chat Model2 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in persuasive email copy, subject lines, hooks, and conversion-focused messaging" 3. Personalization Specialist — model via OpenAI Chat Model3 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in email personalization, custom variables, dynamic content, and individual prospect customization" 4. Email Sequence Strategist — model via OpenAI Chat Model4 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in email sequence design, follow-up timing, nurture campaigns, and multi-touch outreach strategies" 5. Email Deliverability Expert — model via OpenAI Chat Model5 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in email deliverability, spam avoidance, domain reputation, and inbox placement optimization" 6. Outreach Analytics Specialist — model via OpenAI Chat Model6 (gpt-4.1-mini), toolDescription: "call this AI Agent that specializes in email performance tracking, A/B testing, response rate optimization, and campaign analytics" Each Specialist node's text parameter uses the same expression:

    Execution prompt · Source text。Text parameter field of the six Specialist Agent Tool nodes; receives the user message dynamically from the Director at runtime

    ={{ $fromAI('Prompt__User_Message_', ``, 'string') }}
  5. Configure language model nodes and connections

    Add seven OpenAI Chat Model nodes (type @n8n/n8n-nodes-langchain.lmChatOpenAi, version 1.2): - OpenAI Chat Model Director: model set to o3, ai_languageModel output connected to Outreach Director Agent - OpenAI Chat Model1–6: model set to gpt-4.1-mini, each connected to the corresponding Specialist Agent Tool's ai_languageModel input Verify all connections: Chat Trigger → Director; Think → Director (tool); six Specialists → Director (tool); seven Models → respective Agents (language model).

Prompt you can copy

Setup guidance · Editorial suggestion。Hand to setup assistant to confirm inputs and permissions before importing workflow.json or manually recreating nodes

This block is the prompt. Ads are never placed here.

You are setting up the n8n template 6909 multi-agent cold email campaign generator. First confirm: 1) your n8n instance is accessible and an OpenAI API Key credential is configured; 2) you understand the分工: Director Agent uses o3, six Specialist Agent Tools use gpt-4.1-mini; 3) Specialist nodes use `={{ $fromAI('Prompt__User_Message_', ``, 'string') }}` in the text field to dynamically receive user input from the Director, so no fixed prompt is pre-written. If you need to customize a Specialist's system behavior, add it in the agentTool options or an upstream node rather than changing this dynamic expression.

Specialist nodes have no pre-written system prompt; they rely on the Director to dynamically pass the user message. To lock in a fixed role behavior, additional configuration in n8n is required.

Source

Multi-agent cold email campaign generator with O3 Director & GPT-4.1 specialists · yaron-nofluff · n8n.io · 2025-08-02

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related