Automation · Content and publishing

Propose a new GitBook help article from the question that keeps coming up on WhatsApp

An AI agent turns the question you get most on WhatsApp into a GitBook article, in a change request ready for your team to review.

Show me this with my own operation See every automation

How do I turn the questions I get most on WhatsApp into articles in my help center?

You ask your Met on WhatsApp or in the internal chat something like "write a help article on how to change an appointment". The Met lists your GitBook sites, opens the help center's structure to see where it fits and whether something similar already exists, opens a change request, writes the article there with what your team answers on WhatsApp and submits it for review. It sends you the preview link so you can read it before publishing. What is published does not change until someone merges the change request. To write the content and build the preview, the admin has to turn on the generic GitBook API action in Connections, which starts switched off.

What starts it

When someone asks for it

It starts when someone on the team asks the Met for the article on WhatsApp or in the internal chat, with the topic and what customers are usually told. There is no trigger to configure: the Met runs the procedure in that conversation.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Help center content Met with GitBook

This is not a named, seeded Met. It is an internal Met with GitBook connected: it is done when the article sits in a change request submitted for review and it gives you the link to read it, or when it tells you which step it could not do and why.

Run by the content and social Met

Channels: WhatsApp · Website chat

What you need connected

GitBook Automate and collaborate

6 steps · 5 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Find the help center site

The Met lists the documentation sites in your GitBook organization and picks the help center set in the skill. If several have similar names, it asks you which one before going on.
- list_sites GitBook
2
See where the article fits

The Met opens the site's structure and reviews its sections and pages. If a page on the same topic already exists, it tells you instead of duplicating it; if not, it suggests which section the new article goes in.
- get_site_structure GitBook
3
Open a change request

The Met opens a change request in the help center's space, with a title that says which question it answers. That way the article stays as a reviewable draft and what is published does not change.
- create_change_request GitBook
4
Write the article in the draft

With the generic action on, the Met calls the GitBook API operation that writes content into a change request (updateChangeRequestContent) and puts the article there with the answer your team gives on WhatsApp. If the action is off, it stops here and tells you.
- invoke_operation GitBook
5
Submit the change request for review

The Met submits the change request for review so the person in charge approves it in GitBook. The same action can merge and publish; the skill tells it to only submit for review, and if you want it to never merge, the admin turns it off.
- submit_or_merge_change_request GitBook
6
Return the preview link

GitBook does not return a change request's preview in a single call. The Met fetches the space and site data with API operations (getSpaceById and getSiteById) and replies with the link to read the article as it will look once published.
- invoke_operation GitBook

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

A help center or documentation in GitBook

Your company publishes its help center in GitBook, on one of the organization's sites. The Met works on what the connected account can see on that site.
GitBook connected in Met with the generic action on

In Met, open Connections → GitBook → Connect and authorize with an account that can edit the help center. To write the article and build the preview, the admin turns on the generic API action, which starts switched off.
What your team answers on the topic

The answer the team gives on WhatsApp to that question, written in the request or in the Met's skill. The article comes from there; the Met does not make up policies your team never gave.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not publish the article on its own if the skill tells it to only submit for review. Merging the change request is what publishes, and your team should do that in GitBook.
It does not write the content if the generic API action is off: in that case it only opens an empty change request and lets you know.
It does not work out on its own which questions come up most. Someone on the team gives it the topic; the Met builds the article from that information.
It does not ask for confirmation in the chat before writing to GitBook: if the actions are on, it runs them. The admin decides what stays on in Connections.
It does not go through Git Sync. If your help center syncs with a repository, GitBook recommends large changes go through it; this procedure is for a single article.

FAQ

Questions about this automation

No. It stays in a change request, which does not touch what is published. It gets published when someone merges it in GitBook, and this procedure only submits it for review.

Because writing a change request's content and building the preview are GitBook API operations the server calls through a generic action. Since that action opens the API, it starts switched off and the admin turns it on.

This procedure is for a new one: if the Met finds a page on the same topic, it tells you instead of duplicating it. Changing an existing page follows the same change request path.

This procedure only works with GitBook. If your help center lives in Mintlify, Intercom or Contentful, the catalog has its own procedures for those tools.

Keep going