Your runbooks, read and kept current by Neo.
Neo searches and reads your GitBook pages, and drafts page updates in change requests for review.
What Neo does with GitBook.
Search and read
Neo searches your spaces and reads any page as markdown.
Draft updates
Neo writes new and changed pages into a change request.
Review before publish
A merge publishes the change; keep approval on for each one.
Concrete work Neo handles in GitBook.
Find the runbook
Technicians ask a chat agent for the runbook and get its steps.
Docs from tickets
An agent drafts a runbook update from a resolved ticket.
Approved publishing
With approval on, a technician approves each merge before pages go live.
Set it up with Neo.
Connect GitBook
Enter the credentials the GitBook card on Neo's Integrations page asks for. The setup guide shows where to find each one.
Start from a use case
Open the GitBook card's "What Neo can do" tab and press Set up with Neo on the job you want.
Build it with Neo Support
Neo Support picks the tools and the GitBook access the job needs, and builds the agent with you.
Questions about the GitBook integration.
What does Neo need to connect to GitBook?+
The credentials the GitBook card on Neo's Integrations page asks for, from your GitBook account. The setup guide shows where to find each one.
How do I set up one of these use cases?+
Connect GitBook, open its "What Neo can do" tab in the Neo dashboard and press Set up with Neo on the use case. Neo Support builds the agent with you.