Create Help Center drafts with your AI tool

Create with AI helps your AI tool turn supported product behavior into Help Center article proposals. It does not write or publish articles simply because you open the page or copy a prompt.

An Owner or Admin manages this workflow. You need a supported AI tool connected through the local Protodesk MCP adapter and a limited Help Center API key. Browser-based authoring connection is not available yet.

1. Connect your tool

1. Open Help Center → Create with AI → Connect.
2. Create or select an API key with Help Center Read articles and Submit proposals permissions. Do not add customer or conversation permissions just to write documentation.
3. Select your AI tool and enter the installed Adapter path and your deployment's API origin.
4. Follow the generated setup instructions in your AI tool.
5. Use Copy connection check, then run that check in the tool. Confirm that it reports the intended workspace before continuing.

Ask your technical administrator for the adapter and API origin if you do not have them. A key listed on this page is not proof that your AI tool has completed setup. The connection can read existing draft and published Help Center content, so connect only a tool your workspace has approved for that information.

2. Generate a focused batch

1. Open the relevant product repository in your connected AI tool, with permission to use that source material.
2. In Create with AI, select Generate, then Copy authoring prompt.
3. Paste the prompt into the connected tool and specify the reader task or collection you want to cover.
4. Ask it to check existing articles before proposing additions, document supported behavior, and flag anything it cannot verify.

For example: “Prepare setup and troubleshooting guides for our Help Center languages. Reuse existing articles where appropriate, keep new articles unpublished, and note any behavior that still needs verification.”

The local adapter connects the tool to Help Center authoring; it does not automatically inspect your repository. Your AI tool needs its own authorized access to the product material. Exclude credentials, private customer conversations, and unsupported roadmap features from proposed public content.

3. Review what was submitted

Open Review → Open review queue, or select Needs review in the Help Center sidebar. Read the actual submitted content, not just the AI tool's summary of its work.

• New article sets: approval creates unpublished drafts. Review those drafts' language, collection, slug, and content before publishing them separately.
• Updates to published articles: approving the update changes the live article. Check the differences and factual claims before approving.

See Review AI-generated Help Center articles for the review workflow.

If no articles appear

Copying a prompt is not submission. Check whether the AI tool completed its connection check and reported a successful proposal submission. Confirm the workspace, key expiry, and Help Center permissions. A new article set may still be in Needs review rather than All articles.

If an existing article changed while the tool was preparing an update, have it reread the current article before producing a revised proposal. Avoid submitting the same batch repeatedly just because the first result is not yet visible.

After approval and publication, verify the public article before treating the documentation task as complete.