Keep help articles in sync with your product

Your product changes. Your help center stays up to date.

Amendary reads your GitHub changes or public changelog, finds outdated help articles and drafts corrections with evidence. Keep the pages you already have in Notion, GitHub, Zendesk or Intercom, with translation review where supported.

14-day trial, no card. Plans from €39 a month.

Works withNotionGitHubZendeskIntercom

What shipped

Release 2.4: export history is now kept for 90 days

  • Notion

    Data retention

    en
  • GitHub

    docs/exports.md

    enja
  • Zendesk Guide

    Export your data

    endefr
  • Intercom Articles

    Exporting reports

    enes

4 articles, 8 languages ready

An example with made-up articles.

Keep the help center you already use

Notion integration

Help pages and docs edited in place. Your product-updates changelog lives here too.

Connect Notion →
GitHub integration

Markdown in a repo. A fix reaches every language as one commit or pull request.

Connect GitHub →
Zendesk Guide integration

Articles and their translations edited in place. Missing languages are saved as drafts.

Connect Zendesk →
Intercom Articles integration

Articles and their translations edited in place, in US, EU and Australia workspaces. Missing languages are saved as drafts.

Connect Intercom →

From a product change to a corrected help article

A release extends export history from 30 to 90 days. The help article still says 30. Review the correction and the change behind it. This example also shows how the fix reaches existing translations.

This change made 1 article out of date, 2 other languages

Release 2.4: export history is now kept for 90 days.

enExport your dataReady

Sentence now

Export history is kept for 30 days.

Replacement

Export history is kept for 90 days.

Other languages (2)

  • deReady

    Sentence now

    Der Exportverlauf wird 30 Tage lang gespeichert.

    Replacement

    Der Exportverlauf wird 90 Tage lang gespeichert.

  • frReady

    Sentence now

    L’historique des exports est conservé pendant 30 jours.

    Replacement

    L’historique des exports est conservé pendant 90 jours.

One approval sends all ready languages to the live articles. You can dismiss one language alone, and undo the fix in every language it reached.

An example with made-up text, not a real customer. It uses the same language rows as the review queue.

Multilingual support when you need it

Start with the source article. If it has translations, review the same correction in each language.

Fixed once, carried everywhere

The fix is found in the source article, then made in each translation.

Checked by code

Every number, version, URL and name must stay the same. A sentence that cannot be matched is marked Not found. Nothing is guessed.

Missing languages drafted

Amendary can write a missing language for credits. It is saved as a draft in Zendesk or Intercom until you publish it.

Fixes reach every language in GitHub, Zendesk and Intercom. Notion pages are checked one by one. Explore multilingual support →

How it works

  1. 1

    Add a destination

    On Pages, choose Notion, GitHub, Zendesk or Intercom and connect your help center.

  2. 2

    Set what shipped

    On its card, choose what help articles follow: a GitHub repo or your changelog.

  3. 3

    Watch articles

    Browse and pick the articles to keep correct. Translations come with them.

  4. 4

    Approve the fix

    Review the proposed correction and its evidence. Approve the fix or dismiss it. You can undo an applied correction.

How it works, in detail →

Keep articles and translations current

Follow a product release through a proposed correction, review and undo.

Daily checks

Keep every article correct

Each day Amendary reads what shipped and drafts fixes for the articles it made wrong, with the change as proof.

Multilingual support

Keep translations current too

Carry a correction into existing translations, review each language and draft missing translations when you need them.

GitHub, Zendesk, Intercom only
More about multilingual support →

Who it is for

Support and product leads whose help articles need to keep up with frequent product releases.

Support leads

Find the outdated instructions customers are still reading, review a correction and update the article before it causes more support tickets.

Product leads

You ship often and help articles fall behind. See which articles each release touched, with the change as proof.

Public examples

Inspect our own docs

Our help center lives in Notion. The same checks run on GitHub, Zendesk and Intercom articles.

A flat price per team. 14-day trial, no card.

Pay for the help articles you watch, each translation counted as one. Daily checks are included and never metered.

Starter

€39 per month

150 articles, translations included · Unlimited languages, 4 help centers · 2 repos and 15 docs pages

GrowthMost teams

€79 per month

600 articles, translations included · Unlimited languages, 4 help centers · 5 repos and 50 docs pages

Scale

€159 per month

2,000 articles, translations included · Unlimited languages, 4 help centers · 15 repos and 150 docs pages

Free forever with your own Anthropic API key: no limits, model calls billed to your Anthropic account.

Questions we get asked

Can I see a result today?

Yes. Once you watch your articles, run a check from Home on a repo's recent changes: its last release or tag, or its last 5 commits. Any fix it drafts waits in your review queue with the change that caused it. If nothing was made wrong, it says so.

Which help centers does it work with?

Four: Notion, GitHub (a docs folder or wiki), Zendesk Guide and Intercom Articles. Fixes reach every language in GitHub, Zendesk and Intercom. Notion pages are checked one by one.

Does it work with a help center in one language?

Yes. Daily checks find outdated claims in the articles you watch and draft corrections with evidence for your review. If you also maintain translations in GitHub, Zendesk or Intercom, multilingual support carries those corrections into the other languages.

How does a fix reach the other languages?

The model finds the changed sentence in each translation. Code then requires that sentence to match the translation word for word, and every number, version, URL and name in the fix to stay the same. If the sentence is not found, that language is marked Not found and you fix it by hand. One approval sends all ready languages. You can dismiss one language alone.

How do we get started?

On the Pages tab, select Add destination, pick Notion, GitHub, Zendesk or Intercom and sign in. On that destination's card, set what its help articles follow: a GitHub repo or your public changelog. Then browse and watch the articles to keep correct.

Can we review changes first?

Yes. Every workspace starts with review before publishing. Paid plans, and teams on their own Anthropic key, can apply supported corrections automatically; risky edits still wait for a person. Applied corrections can be undone for 30 days, provided the text has not changed since.

What happens to our code and docs?

Amendary reads the relevant code and page content to do its work, and sends selected context to its AI provider. It never edits your code. You choose which pages to watch. The Security page explains access, storage and retention.

What is included in the trial?

You get 14 days of daily checks for 1 repo, 1 help center in up to 2 languages, 50 help articles (translations included) and 10 docs pages, with every edit reviewed by you. No card is required. You can also try a free sample page before a full generation run.

More in the Help Center.

Keep your help center ready for the next release.

Free for 14 days with no card, or free forever with your own Anthropic API key. During the trial, every edit waits for your review.

Get started free