Slack + Google Docs: HR requests turned into drafts
Your HR inbox is full of “quick questions” that are never quick. Someone drops a messy Slack message about onboarding, a policy update, or a tricky performance situation, and suddenly you’re rewriting the same doc (again) while trying not to miss something important.
This hits HR managers first. But ops leads and founders feel it too, because they end up approving drafts that are inconsistent, incomplete, or just hard to trust. A simple Slack Docs drafts automation turns those messages into clean, structured Google Docs drafts you can edit and approve.
Below is the exact workflow, what it automates, and what results you should expect when you stop treating every HR request like a blank page.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Slack + Google Docs: HR requests turned into drafts
flowchart LR
subgraph sg0["When chat message received Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When chat message received", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "CHRO Agent", pos: "b", h: 48 }
n2@{ icon: "mdi:wrench", form: "rounded", label: "Think", pos: "b", h: 48 }
n3@{ icon: "mdi:wrench", form: "rounded", label: "Recruiter Agent", pos: "b", h: 48 }
n4@{ icon: "mdi:wrench", form: "rounded", label: "HR Policy Writer", pos: "b", h: 48 }
n5@{ icon: "mdi:wrench", form: "rounded", label: "Training & Development Speci..", pos: "b", h: 48 }
n6@{ icon: "mdi:wrench", form: "rounded", label: "Performance Review Specialist", pos: "b", h: 48 }
n7@{ icon: "mdi:wrench", form: "rounded", label: "Employee Engagement Specialist", pos: "b", h: 48 }
n8@{ icon: "mdi:wrench", form: "rounded", label: "Compensation & Benefits Anal..", pos: "b", h: 48 }
n9@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model CHRO", pos: "b", h: 48 }
n10@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model1", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model2", pos: "b", h: 48 }
n12@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model3", pos: "b", h: 48 }
n13@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model4", pos: "b", h: 48 }
n14@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model5", pos: "b", h: 48 }
n15@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model6", pos: "b", h: 48 }
n2 -.-> n1
n3 -.-> n1
n4 -.-> n1
n10 -.-> n3
n11 -.-> n4
n12 -.-> n5
n13 -.-> n6
n14 -.-> n7
n15 -.-> n8
n9 -.-> n1
n0 --> n1
n6 -.-> n1
n7 -.-> n1
n8 -.-> n1
n5 -.-> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n1 ai
class n9,n10,n11,n12,n13,n14,n15 aiModel
class n2,n3,n4,n5,n6,n7,n8 ai
The Problem: HR Requests Start in Slack, Then Spiral
Slack is where HR requests land because it’s easy for employees. It’s also where clarity goes to die. A single message can mix context, emotions, missing details, and a vague “can you draft something?” into one paragraph. Then comes the chase: follow-up questions, rewrites, approval loops, and version confusion. Even if you’re good at writing, you still waste time reformatting and trying to keep tone consistent across policies, onboarding plans, interview kits, and performance templates. Frankly, it’s not the hard HR work that drains you. It’s the repetitive doc creation.
The friction compounds. Here’s where it breaks down in real teams.
- You spend about 30 minutes turning a Slack message into a usable first draft, and then you do it again tomorrow.
- Details arrive in fragments, so drafts go out incomplete and approvals bounce back with “add more context.”
- Style and structure drift, which makes your HR docs feel like they were written by five different companies.
- Policy work and performance templates get delayed because “quick requests” keep interrupting deeper projects.
The Solution: An AI HR Team That Turns Requests Into Drafts
This workflow gives you a “virtual HR department” inside n8n. A chat intake trigger receives the HR request, and a Chief HR Orchestrator (the CHRO agent) reads it like a senior HR lead would: what’s being asked, what’s missing, what format the output should take, and which specialist should handle it. Then it delegates the work to the right agent (recruiting, policy, training, performance, engagement, or compensation). Each specialist generates a structured deliverable using an OpenAI chat model. Instead of a messy response blob, you get a consistent draft you can drop into your existing approval process and refine quickly.
The workflow starts when a request comes in through chat. The CHRO agent routes it to one or more HR specialists, and the system produces a polished draft output (for example, an onboarding plan, a handbook policy section, or interview questions). With a Google Docs layer added, that output becomes a ready-to-edit doc instead of something you paste around in Slack.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your team handles 15 HR requests a week in Slack, and each one takes about 30 minutes to turn into a decent doc draft (collecting context, writing, formatting, and sending it for review). That’s roughly 7–8 hours a week. With this workflow, you submit the request in chat (maybe 2 minutes), wait a few minutes for the agents to generate the deliverable, and then you do a fast edit pass (about 10 minutes). Call it 3 hours total for the week. That’s basically half a day back, without hiring anyone.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Slack to capture HR questions where they already happen.
- Google Docs to store drafts in a sharable format.
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You’ll connect credentials, adjust prompts, and test a few sample HR requests end-to-end.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A request comes in through chat. The workflow begins with a chat intake trigger, which means your HR team can submit requests in plain English without filling out a form.
The CHRO agent interprets the ask. This is the “senior brain” that identifies intent (policy vs. hiring vs. performance), spots missing details, and decides which specialist agent should draft the deliverable.
Specialists generate structured drafts. The workflow can call a recruiter agent for interview kits, a policy writer for handbook updates, or a training specialist for onboarding plans. These are separate chat models, tuned for speed and cost, which keeps output consistent.
The draft is ready for Google Docs. In practice, you can take the final text output and create a Google Doc draft (or append to an existing doc) so approvals happen in a proper document, not inside Slack.
You can easily modify the output format to match your internal templates based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
Set up the entry point so HR questions can be sent into the workflow and routed to the orchestrator.
- Add and open Chat Intake Trigger.
- Leave the default Options as configured (
{}). - Confirm the execution flow: Chat Intake Trigger → Chief HR Orchestrator.
Step 2: Connect OpenAI
All language models in this workflow are OpenAI-based and require credentials.
- Open Executive Chat Model and set Model to
o3. Credential Required: Connect your openAiApi credentials. - Open Recruitment Chat Model, Policy Chat Model, Training Chat Model, Performance Chat Model, Culture Chat Model, and Compensation Chat Model and set Model to
gpt-4.1-minifor each. Credential Required: Connect your openAiApi credentials to each node.
Note: AI tool nodes like Reflection Step and the advisor tools do not store credentials—credentials must be added to their connected chat model nodes.
Step 3: Set Up Chief HR Orchestrator
The orchestrator agent coordinates which specialized advisor should respond to the incoming chat.
- Open Chief HR Orchestrator and keep the default Options (
{}). - Connect Executive Chat Model to Chief HR Orchestrator as the AI Language Model.
- Verify the trigger connection from Chat Intake Trigger into Chief HR Orchestrator.
Step 4: Configure Advisor Tools
Each advisor tool specializes in a different HR topic and is invoked by the orchestrator.
- Open Reflection Step and connect it to Chief HR Orchestrator as an AI tool for internal reasoning.
- For each advisor tool—Talent Acquisition Advisor, Policy Drafting Advisor, Learning Program Advisor, Performance Review Guide, Engagement Culture Coach, and Rewards Analysis Consultant—set Text to
{{ $fromAI('Prompt__User_Message_', ``, 'string') }}. - Confirm each advisor’s Tool Description matches its HR specialization (recruitment, policies, training, performance, engagement, compensation).
Step 5: Configure Advisor Chat Models
Each advisor tool uses its own language model; link each tool to its chat model.
- Connect Recruitment Chat Model to Talent Acquisition Advisor as the AI Language Model.
- Connect Policy Chat Model to Policy Drafting Advisor as the AI Language Model.
- Connect Training Chat Model to Learning Program Advisor as the AI Language Model.
- Connect Performance Chat Model to Performance Review Guide as the AI Language Model.
- Connect Culture Chat Model to Engagement Culture Coach as the AI Language Model.
- Connect Compensation Chat Model to Rewards Analysis Consultant as the AI Language Model.
Step 6: Test and Activate Your Workflow
Validate that chat requests are routed to the correct advisor and responses return as expected.
- Click Execute Workflow and send a sample HR prompt through Chat Intake Trigger (e.g., “Draft a parental leave policy”).
- Confirm Chief HR Orchestrator selects the correct advisor tool and returns a coherent response.
- If the response is missing, recheck that all advisor tools are connected to their respective chat models and that OpenAI credentials are valid.
- Once validated, toggle Active to enable the workflow for production use.
Common Gotchas
- OpenAI credentials can expire or be scoped incorrectly. If things break, check your n8n credential settings and your OpenAI dashboard billing/limits first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 45 minutes if your Slack, Google, and OpenAI accounts are ready.
No. You’ll connect accounts and edit a few prompts and fields inside n8n.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per request depending on length and model.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but you’ll want to do it intentionally. You can adjust the CHRO agent’s instructions so it always outputs in your preferred structure (for example: purpose, scope, definitions, policy text, and manager notes). Common customizations include forcing a specific tone, requiring “assumptions + open questions” at the top, and routing certain topics (like compensation) to a stricter approval path. If you later swap the final destination, you can keep the same draft text and simply change where it gets written (Google Docs, a knowledge base, or even a ticketing tool).
Usually it’s an invalid or expired API key, or your OpenAI project has billing limits that stop requests. Update the credential in n8n, then check usage and rate limits in your OpenAI dashboard. If it fails only on long requests, reduce the requested output size or split the deliverable into smaller sections so the model doesn’t time out.
For most small teams, it can handle hundreds of requests a month without drama.
Often, yes, because this is not a simple “send message, create doc” zap. n8n handles multi-agent routing, branching logic, and richer prompt control in one workflow. It also gives you a self-hosting option if you want to scale without paying per-task pricing. Zapier or Make can still be fine if you only need a basic two-step automation and don’t care about specialist agents. Talk to an automation expert if you want help choosing.
Once this is in place, HR requests stop derailing your day. You get clean drafts, faster approvals, and a process your team can actually stick to.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
