Zendesk Guide integration

Your source-language articles, drafts marked as Draft, and their translations. Categories and sections are read to show the browse tree.

For each article you watch, Amendary reads the title and body and keeps a short list of what the article claims.

What shipped comes from the connection’s card, under Help articles follow: a GitHub repo, or each new entry on your public changelog.

The body of the articles you watch, and nothing else. Titles, sections and settings stay as they are.

A fix never changes whether an article or a language is published or a draft.

A missing language can be drafted for credits. It is saved as a draft. Amendary never publishes an article.

Zendesk asks you to allow two scopes: hc:read and hc:write. That is Help Center content only. Amendary cannot see tickets, users or any other part of Zendesk.

Zendesk gives a short-lived access token and a refresh token. Both are stored encrypted. Amendary renews the access token on its own. If Zendesk refuses, the card shows Sign in again.

1. Once a day, Amendary checks what shipped against the articles you watch.
2. It drafts the fix for the source article, with the change as evidence. Then it fixes the same sentence in each translation. A language is marked Check it when a number, version, URL or name does not match.
3. New teams start on Review first: every fix waits for you. On Apply automatically (paid plan or your own key), a fix still waits when it states a value the change does not back up, removes content, or adds new text.
4. Before writing, Amendary reads the live article again. If someone changed it since, the fix is not written.

Undo is in the Queue for 30 days. It writes the old text back, but only if nobody edited the article since.

A workspace owner can disconnect on the Pages tab. Amendary asks Zendesk to revoke its access token, then deletes the stored tokens, the connection, its watched articles and their fixes. Nothing in Zendesk changes.

Generate docs writes new articles into a section you pick. Each one is saved as a draft, with the same visibility as the other articles in that section, and is then watched like any article. You publish it in Zendesk.

Cleanup checks the articles you pick against your code and says which to keep, fix or retire, with the proof. It never edits an article.

Both spend credits, shown before the run. Diagrams and product updates are Notion only.

• Keep your Zendesk help center current: the problem, outcome and a multilingual example
• Update Zendesk articles after a release: follow the workflow after connecting
• Connect Zendesk Guide: sign in step by step
• Multilingual support: how a fix reaches every language
• Help-center languages: set languages and draft missing ones
• Review and undo: what waits for you and how undo works
• What shipped: a GitHub repo or a changelog URL
• Compare with Zendesk's knowledge tools: what each one does
• Security: what is stored, sent and deleted