GPT-5 + Google Docs: polished bios from one message
Your “quick bio update” turns into a time sink. You open an old document, copy chunks from LinkedIn, rewrite half of it, then still wonder if it sounds like you.
This is the kind of mess that slows down marketers during launches, hits founders right before a big announcement, and quietly drains agency teams when client profiles need to stay consistent. With this bio automation, one message becomes a polished biography and lands in Google Docs ready to approve.
You’ll see how the workflow drafts, reviews, and refines with GPT-5, then updates a Doc automatically (so bios don’t live in a dozen places).
How This Automation Works
See how this solves the problem:
n8n Workflow Template: GPT-5 + Google Docs: polished bios from one message
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: "Biography Agent", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Evaluator Agent", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Evaluate", pos: "b", h: 48 }
n4@{ icon: "mdi:robot", form: "rounded", label: "Optimizer Agent", pos: "b", h: 48 }
n5@{ icon: "mdi:cog", form: "rounded", label: "Push to Docs", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Bio", pos: "b", h: 48 }
n7@{ icon: "mdi:brain", form: "rounded", label: "GPT-5", pos: "b", h: 48 }
n7 -.-> n1
n7 -.-> n2
n7 -.-> n4
n6 --> n2
n3 --> n5
n3 --> n4
n1 --> n6
n2 --> n3
n4 --> n6
n0 --> 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,n2,n4 ai
class n7 aiModel
class n3 decision
The Challenge: Bios That Never Stay “Final”
Bios are deceptively hard. They look short, but they carry a lot: credibility, tone, clarity, and the “what do you actually do?” question. Most teams end up with five versions scattered across places that don’t sync. Someone pastes an outdated paragraph into a speaker form, another person trims it for a website, and now you’re back to chasing edits. The time cost is annoying, but the mental load is worse because every update feels like starting over.
It adds up fast. Here’s where it usually breaks down.
- Each bio request pulls you into a mini writing project, even when you already have the raw details.
- Consistency falls apart across platforms, so your LinkedIn voice and website voice drift over time.
- Teams end up doing “editing by committee” in chat, which means lots of opinions and no clean final draft.
- Copy-paste workflows invite small errors like wrong titles, old locations, or stale accomplishments.
The Fix: Draft + Review + Refine, Then Save to Google Docs
This workflow turns one chat-style message into a finished bio you can actually use. It starts when you send basic details (name, location, what you do, what you want to emphasize). GPT-5 writes a complete first draft in your chosen style, not a stiff template. Then a second agent reads that draft like an editor would and returns structured feedback, calling out weak phrasing, missing context, or tone issues. If the review says it needs work, a refinement agent rewrites the bio using that feedback, so you aren’t stuck doing “edits on top of AI.” Finally, the workflow updates a Google Doc so your approved bio lives in one dependable place.
The flow begins with chat intake. From there, the draft is generated, evaluated, and either approved or improved. When it passes the completion check, it’s written straight into Google Docs and stored as clean text for reuse.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say your team needs 6 bios refreshed for a website update. Manually, a typical cycle is about 30 minutes to draft per person plus about 15 minutes of edits and back-and-forth, so roughly 4–5 hours total. With this workflow, you send one message per person (maybe 2 minutes each), let GPT-5 draft and refine, then review the final output in Google Docs. That’s usually under an hour end-to-end for all six, with fewer “can you tweak this line?” detours.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Docs for saving and sharing the final bios
- Google account access to connect the Docs integration
- OpenAI API key (get it from the OpenAI dashboard)
Skill level: Beginner. You’ll connect accounts and tweak prompts, but you won’t be writing code.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Chat intake kicks it off. You send a single message with the raw details you already have, like role, audience, and a couple of proof points.
A drafting agent writes the first version. GPT-5 generates a complete bio in one pass, guided by a prompt that sets tone and formatting rules.
An evaluator reads it like an editor. A second agent returns feedback in a structured way, which is useful because it’s specific enough to act on.
A completion check decides what happens next. If the evaluator signals the bio is good, it moves forward. If not, the refinement agent rewrites it and stores the improved text.
Google Docs gets the final version. The workflow updates your chosen Doc automatically so the “approved bio” is easy to find, copy, and reuse.
You can easily modify the tone and formatting rules to match your brand voice 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 workflow entry point so biographies begin when a chat message arrives.
- Add the Chat Intake Trigger node as the trigger for the workflow.
- Keep Options empty unless you need custom chat trigger behavior.
Step 2: Set Up the Draft and Storage Flow
Create the initial biography and store it for review and refinement.
- In Profile Draft Agent, set the System Message to
=# Overview You are an expert biography writer. You will receive information about a person, and your job is to create an entire profile using the information they give you. You are allowed to be creative.. - Connect Chat Intake Trigger → Profile Draft Agent → Store Bio Text.
- In Store Bio Text, set the bio assignment to
={{ $json.output }}so the agent’s output is captured.
Credential Required: Connect your openAiApi credentials in OpenAI Chat Model. The language model is used by Profile Draft Agent, Bio Review Agent, and Bio Refinement Agent via the shared model connection.
Step 3: Configure Review, Completion Logic, and Refinement
Review the draft biography, check if it meets criteria, and refine if needed.
- In Bio Review Agent, set Text to
=Here is the biography: {{ $json.bio }}and keep Prompt Type as define. - Connect Store Bio Text → Bio Review Agent → Completion Check.
- In Completion Check, configure the condition to compare Left Value
={{ $json.output }}equalsFinished. - In Bio Refinement Agent, set Text to
=Biography: {{ $('Store Bio Text').item.json.bio }} Feedback: {{ $('Bio Review Agent').item.json.output }}and keep Prompt Type as define. - From Completion Check, route the “false” output to Bio Refinement Agent, then back to Store Bio Text for another review loop.
Completion Check outputs to both Update Docs File and Bio Refinement Agent in parallel, depending on whether the condition is met.
Step 4: Configure Output to Google Docs
Write the finalized biography into a Google Docs file.
- In Update Docs File, set Operation to update.
- Set Document URL to your actual document link (replace
Add your document URL). - In Actions, set the Text to insert as
={{ $('Store Bio Text').item.json.bio }}.
Credential Required: Connect your googleDocsOAuth2Api credentials.
⚠️ Common Pitfall: Leaving the Document URL as Add your document URL will cause the update to fail. Paste the full Google Docs URL.
Step 5: Test and Activate Your Workflow
Validate the workflow end-to-end and then enable it for production use.
- Click Execute Workflow and send a sample chat message to Chat Intake Trigger.
- Verify that Store Bio Text receives a bio value and that Bio Review Agent outputs either feedback or
Finished. - If the output is
Finished, confirm that Update Docs File inserts the biography into your Google Doc. - Once validated, toggle the workflow to Active for live use.
Watch Out For
- Google Docs credentials can expire or need specific permissions. If things break, check the n8n “Credentials” screen and your connected Google account access 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.
Common Questions
About 30 minutes if your accounts are already connected.
Yes. No coding is required, but someone should be comfortable connecting Google Docs and pasting an API key.
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 small for short bios.
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.
You can change the writing style by editing the prompt inside the Profile Draft Agent and Bio Refinement Agent. Common tweaks include adding a “first-person vs third-person” rule, forcing a word limit for speaker pages, and inserting a short tagline line at the top before the main paragraph. If you want a stricter approval gate, tighten the Completion Check so only “approved” evaluator feedback can reach Google Docs.
Usually it’s expired Google credentials or the wrong Google account connected in n8n. Reconnect the Google Docs credential, then confirm the Doc you’re updating is accessible to that account. If it fails only sometimes, you may also be hitting temporary Google API limits when running many bios back-to-back.
On n8n Cloud Starter you can run a healthy volume each month for small teams, and self-hosting removes the execution cap (your server becomes the limit). In practice, the bottleneck is usually the GPT-5 calls and how fast you want to review outputs, not n8n itself.
Often, yes, because this workflow relies on multi-step logic: draft, evaluate, conditionally refine, then update Google Docs. n8n handles branching and multi-agent chains without making you pay extra for every path, and you can self-host if volumes grow. Zapier or Make can still work, but the evaluator/refinement loop tends to feel awkward there. Also, prompt management matters a lot with bios, and n8n makes it easier to keep prompts in one place. If you’re unsure, Talk to an automation expert and get a straight recommendation based on your volume and tools.
Once this is in place, bios stop being a recurring writing emergency. The workflow handles the drafting and polishing, and you just approve what looks right.
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.
