Amendary can connect directly to Zendesk Guide or Intercom Articles and keep those live help-center articles correct, not just Notion or GitHub docs.
On the Pages tab, choose the Zendesk or Intercom service and sign in with OAuth (or, in development, paste an API token). Once connected, add it as a help center: pick what shipped feeds it, either a GitHub repo's releases and commits, or a public changelog URL that Amendary reads daily.
Browse the help center's folders and articles and choose which ones to watch. Watching an article watches all of its languages: the source-language article becomes the one that gets checked and corrected, and each translation is tracked alongside it.
When a change makes the source article wrong, Amendary drafts the fix for the source language as usual. That same fix is then carried into every watched translation: the model locates the matching sentence in each language and drafts its correction, and code checks that every number, version, URL and product name stayed the same before the translation fix is allowed through. A translation whose fix can't be verified is held for a person to confirm by hand, named in the queue card.
Approving the source-language correction also delivers the fixes to its translations. Rejecting the source correction leaves the translations untouched.
A Zendesk or Intercom article that is still a draft stays a draft: Amendary writes the body in place but never changes an article's published state. The same applies to a brand-new translation it creates for a target language you haven't translated yet, offered from the article's row: it's saved as an unpublished draft for the team to review and publish.
Help-center corrections go through the same review queue and review modes (manual or auto-apply) as any other watched page. Each plan has separate limits for help centers, articles, and target languages per help center, shown on the Plan settings page alongside the existing repo and docs-page limits.