GitBook

Documentation is the first thing users read and the last thing teams keep updated. In this webinar, GitBook and n8n team up to show how AI and automation are changing that. We'll cover how to automate docs updates end-to-end, what GitBook's AI insights reveal about what your users actually need, and how n8n's own team uses GitBook to run a fully open, community-driven docs workflow. GitBook transforms documentation into an intelligent knowledge system that connects content, context, and AI — so your docs don’t just exist, they actively learn and get better over time. Learn more: ✨ Get started for free: https://app.gitbook.com/join 📚 Explore the docs: https://gitbook.com/docs 🌐 Visit GitBook: https://gitbook.com Chapters: 0:00 Waiting room & housekeeping 1:09 Introductions — Addison (GitBook) & Karthik (n8n) 4:00 Why docs go stale 6:15 n8n's approach: treating docs updates as signals 7:09 Demo: GitHub PR tagging & repo hygiene workflow 12:20 Demo: auto-generating environment variable docs 15:54 GitHub as source of truth + GitBook live previews 19:05 The evolving writer role & daily PR review 21:55 DocFather bot: Slack digests & analytics 23:20 Drafting docs with AI from Linear issues 28:16 Inside the DocFather agent workflow 31:42 GitBook's toolkit: four pillars for automated docs 35:24 Feedback: analytics & AI insights 37:23 Making updates: Channels, MCP server & CLI 38:49 Guardrails: style guides & agent skills 40:50 Signals: the upcoming Triage feature 41:53 Takeaways: the docs flywheel 43:50 Q&A 45:27 Q&A: managing community contributions & spam 48:40 Q&A: getting started with n8n & what to automate first 52:07 Wrap-up

Docs fall behind because updating them means context-switching. GitBook Channels fixes that. Product teams consistently tell us that keeping documentation up to date with product changes is their #1 challenge — not because they don't care, but because the friction of switching tools makes it easy to defer. GitBook Channels brings documentation workflows into the tools your team already uses. Now, kicking off a change request is as simple as mentioning @GitBook in a thread. No tab-switching, no lost context, no docs left behind. In this video, we'll show you how Channels works and how teams are using it to close the gap between shipping product changes and updating the docs that explain them. GitBook transforms documentation into an intelligent knowledge system that connects content, context, and AI — so your docs don’t just exist, they actively learn and get better over time. Learn more: ✨ Get started for free: https://app.gitbook.com/join 📚 Explore the docs: https://gitbook.com/docs 🌐 Visit GitBook: https://gitbook.com Chapters: 0:00 Waiting room & housekeeping 2:05 Welcome & agenda 4:08 What are GitBook Channels? (GitHub, Slack & Linear) 5:55 Demo setup: the Syncly docs site & new UI 7:33 Where to find Channels in site settings 7:55 GitHub channel: support agent vs. collaborator 9:15 GitHub demo: documenting a new feature PR 10:53 Linear channel: setup & documenting a ticket 13:03 Slack channel: setup & restricting access 15:31 Slack demo: updating docs from a thread 17:03 Reviewing what the agent did in each tool 18:45 Working with change requests in GitBook 20:26 The new GitBook Agent editing screen 21:33 Reviewing & merging change requests 24:00 Customizing GitBook Agent with instructions 25:20 Q&A (Slack approval, releases page, Intercom/Zendesk, Jira & more) 30:20 Wrap-up