Update Article
hudu_update_articleIdempotent
Update an existing Hudu knowledge-base article by replacing one or more of its fields. Pass only the fields to change; each supplied value wholly replaces the stored one.
Instructions
Update an existing article. An article is a knowledge-base document: HTML content, optionally filed in a folder and optionally scoped to one company. Articles with no company are global to the instance.
Only the fields you supply are sent. Be aware that Hudu applies these as a PUT: for fields you do send, the new value replaces the old one outright — read the record first with hudu_get_article if you intend to append rather than overwrite.
Operation class: Update. Impact: Overwrites the supplied fields on this article.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric Hudu id of the article. | |
| name | No | Title of the article, shown in lists and search. | |
| content | No | Body of the article, as HTML. Hudu stores this string and renders it as HTML in the knowledge base, so Markdown passed here is stored literally and shown to readers with its asterisks, hashes and pipes intact — convert to HTML (<h2>, <p>, <ul>, <table>, <a href="...">) before sending. Existing content is replaced wholesale on update, not appended to. | |
| folder_id | No | Numeric id of the folder to file the article under, from hudu_list_folders. Omit to leave the article at the top level. Pick a folder whose own company matches the article's — Hudu does not document what it does with a mismatch. | |
| company_id | No | Numeric id of the company whose knowledge base this article belongs to. Omit it to create a global article that is visible across every company. Resolve a customer name to an id with hudu_list_companies first. | |
| enable_sharing | No | PUBLISHES THIS ARTICLE TO THE PUBLIC INTERNET when set to true. Hudu mints a share URL (returned as `share_url` on the record) that renders the full article content to anyone holding the link, with no Hudu login, no company scoping and no record of who read it. Client documentation frequently contains internal hostnames, procedures and account references, so treat this as a disclosure decision rather than a formatting one: leave it unset unless the user has explicitly asked for a link they can send outside their Hudu tenant, and tell them what the article contains before you set it. Setting it to false withdraws an existing public URL. |