Skip to main content

Collaborative sales planning with multi-agent AI, Google Docs, and Slack

Workflow preview

Workflow preview
100%
Collaborative sales planning with multi-agent AI, Google Docs, and Slack preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Multi Agent Architecture Free Bootstrap Template for Beginners [![Watch the video](https://wisestackai.s3.ap southeast 1.amazonaws.com/n8n multi agent architecture free bootstrap template for begin...

Best for

  • Document Extraction automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.agenttool, n8n-nodes-base.httprequest, n8n-nodes-base.slack, n8n-nodes-base.googledrive

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Trung Tran.

Original n8n.io source

1.1 Workflow description

Title
Collaborative sales planning with multi-agent AI, Google Docs, and Slack
Workflow name
Collaborative sales planning with multi-agent AI, Google Docs, and Slack

Multi-Agent Architecture Free Bootstrap Template for Beginners

Free template to learn and reuse a multi-agent architecture in n8n. The company metaphor: a CEO (orchestrator) delegates to Marketing, Operations, Finance to produce a short sales-season plan, export it to PDF, and share it.

Who’s it for

  • Builders who want a clear, minimal pattern for multi-agent orchestration in n8n.
  • Teams demoing/teaching agent collaboration with one coordinator + three specialists.
  • Anyone needing a repeatable template to generate plans from multiple “departments”.

How it works / What it does

  1. Trigger (Manual) — Click Execute workflow to start.
  2. Edit Fields — Provide brief inputs (company, products, dates, constraints, channels, goals).
  3. CEO Agent (Orchestrator) — Reads the brief, calls 3 tool agents once, merges results, resolves conflicts.
  4. Marketing Agent — Proposes top campaigns + channels + content calendar.
  5. Operations Agent — Outlines inventory/staffing readiness, fulfillment steps, risks.
  6. Finance Agent — Suggests pricing/discounts, budget split, targets.
  7. Compose Document — CEO produces Markdown; node converts to Google Doc → PDF.
  8. Share — Upload the PDF to Slack (or Drive) for review.

Outputs

  • Markdown plan with sections (Summary, Timeline, Marketing, Ops, Pricing, Risks, Next Actions).
  • Compact JSON for automation (campaigns, budget, dates, actions).
  • PDF file for stakeholders.

How to set up

  1. Add credentials
    • OpenAI (or your LLM provider) for all agents.
    • Google (Drive/Docs) to create the document and export PDF.
    • Slack (optional) to upload/share the PDF.
  2. Map nodes (suggested)
    • When clicking ‘Execute workflow’Edit Fields (form with: company, products, audience, start_date, end_date, channels, constraints, metrics).
    • CEO Agent (AI Tool Node) → calls Marketing Agent, Operations Agent, Finance Agent (AI Tool Nodes).
    • Configure metadata (doc title from company + window).
    • Create document file (Google Docs API) with CEO Markdown.
    • Convert to PDF (export).
    • Upload a file (Slack) to share.
  3. Prompts (drop-in)
    • CEO (system): orchestrate 3 tools; request concise JSON+Markdown; merge & resolve; output sections + JSON.
    • Marketing / Operations / Finance (system): each returns a small JSON per its scope (campaigns/calendar; staffing/steps/risks; discounts/budget/targets).
  4. Test — Run once; verify the PDF and Slack message.

Requirements

  • n8n (current version with AI Tool Node).
  • LLM credentials (e.g., OpenAI).
  • Google credentials for Docs/Drive (to create & export).
  • Optional Slack bot token for file uploads.

How to customize the workflow

  • Swap roles: Replace departments (e.g., Product, Legal, Support) or add more tool agents.
  • Change outputs: Export to DOCX/HTML/Notion; add a cover page; attach brand styles.
  • Approval step: Insert Slack “Send & Wait” before PDF generation for review/edits.
  • Data grounding: Add RAG (Sheets/DB/Docs) so agents cite inventory, pricing, or past campaign KPIs.
  • Automation JSON: Extend the schema to match your CRM/PM tool and push next_actions into Jira/Asana.
  • Scheduling: Replace manual trigger with a cron (weekly/monthly planning).
  • Localization: Add a Translation agent or set language via input field.
  • Guardrails: Add length limits, cost caps (max tokens), and validation on agent JSON.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - CEO Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 2.1

Block 3 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 4 - Edit Fields

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 5 - OpenAI Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 6 - OpenAI Chat Model2

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 7 - Marketing Agent

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 2.2

Block 8 - Operations Agent

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 2.2

Block 9 - Finance Agent

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 2.2

Block 10 - OpenAI Chat Model3

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 11 - Create document file

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 12 - Configure metadata

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 13 - Upload a file

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 14 - Convert to PDF

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 15 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Collaborative sales planning with multi-agent AI, Google Docs, and Slack
Complexity advanced
Nodes 24
Categories Document Extraction, Multimodal AI
Author Trung Tran
Published 17 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7504/7504.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Collaborative sales planning with multi-agent AI, Google Docs, and Slack do?

Multi Agent Architecture Free Bootstrap Template for Beginners [![Watch the video](https://wisestackai.s3.ap southeast 1.amazonaws.com/n8n multi agent architecture free bootstrap template for begin...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, Multimodal AI use case.