Update the existing KB article when correcting a procedure, refreshing a link or improving its wording. A read-before-write workflow preserves the page’s identity and reduces the chance of overwriting somebody else’s work.

Read the current article first

Use a dedicated content connection with a Write ceiling, the required content area and staff permissions. The separate read-only override must permit the intended write. The bound administrator needs Manage Knowledgebase in its administrator role. A connection limited to selected clients cannot operate on the shared knowledge base.

Ask the assistant to Read a knowledge base article using the exact article ID. Confirm the title, full body, categories, access and available language versions. A short search excerpt is not enough to prepare a complete body replacement.

Agree the specific change and keep the current content available for comparison. If another editor has changed the article since the review, reconcile those edits rather than applying the earlier replacement blindly.

Submit only the intended changes

The article update can change the title, body, access, category list or tags. If you supply category_ids, it replaces the complete category selection; supplying tags replaces the tag set. Include the full intended list when changing either, and omit the field when it should stay as it is.

For a translation, specify its language as well as the existing main article ID. Title and body then target that translation, while any supplied access, categories or tags still change the main article’s shared settings. Keep a translation-only edit limited to the intended language text.

1. Confirm the existing article ID and target language.
2. Review the finished replacement text or the specific metadata changes.
3. Authorise Edit a knowledge base article with only the fields that should change.
4. Review a pending approval if the connection requires one.
5. Read the same article back and compare it with the agreed result.

A body edit sends the complete replacement body; describing a paragraph to change does not by itself establish what the tool will save. Ask the assistant to preserve the remaining text and show the intended result before the write.

Verify content and audience

Check that earlier links, headings and any user edits remain unless their removal was intended. Confirm categories and visibility separately from text. Then inspect the native article page as the intended reader.

If the request returns an error or an uncertain result, read the article again before retrying. Do not use Delete and Add as an update shortcut: deletion is a different operation with broader consequences, and recreating content does not preserve the article’s identity.

See the PD MCP Hub WHMCS guide for related tasks, or explore PD MCP Hub.