HC Article Updater

If multiple sources are provided, read them all and synthesize. Prioritize the most recently approved wording — often a Slack thread will contain iterative drafts; the last agreed version is what matters.

Key things to extract:

• What specifically changed (old behavior → new behavior)
• The exact approved text (if any) to use in the article
• The scope: which user groups or plans are affected
• Any caveats or edge cases mentioned

Summarize your understanding to the user in 2-3 sentences before proceeding, so they can catch misinterpretations early.

Step 2 — Navigate to the HC section

The user will provide a Zendesk Help Center section URL (e.g. https://help.vimeo.com/hc/en-us/sections/44977868355345-Billing).

Use Claude in Chrome to navigate there. Browse the article list. If the section has pagination ("Next →"), click through all pages.

For each article, note:

• Its title
• Its URL / article ID
• Whether it's internal-only ("Only visible to agents and admins")

You're looking for articles whose content is likely to be affected by the change you extracted in Step 1. Use judgment: titles like "Lapsing from a paid account", "Storage limits", "What happens when I downgrade" are relevant to a storage policy change; titles like "How to add a team member" are not.

If the user already named a specific article, go directly to it. If uncertain, briefly tell the user which articles you plan to read and why, and confirm before reading all of them.

Step 3 — Read each candidate article

Navigate to each article (the public HC URL, not the editor). Use get_page_text to read the full content.

While reading, identify:

• The specific section(s) that reference the old behavior
• The exact current wording that needs to change
• Anything that contradicts the new policy or feature

Keep track of: article title, URL, article ID (the number in the URL), and the specific text to change.

Step 4 — Draft all changes for review

Before touching anything, present every proposed change to the user in this format:

### Article: [Title]
URL: https://...

**Section:** [Section heading, e.g. "What happens to my videos when my plan lapses to Free?"]

**CURRENT TEXT:**
> [exact current paragraph(s)]

**PROPOSED NEW TEXT:**
> [new paragraph(s) with the change applied]

If multiple articles need updating, list them all in one message. Be precise: only change what needs to change. Don't rewrite surrounding paragraphs that are correct.

End with: "Does this look right? Reply 'apply' to publish all changes, or give me feedback to revise."

Do not proceed until the user explicitly approves (e.g., "apply", "looks good", "yes", "go ahead").

Step 5 — Apply and publish each article

For each article to update, follow the technical steps in references/zendesk-editor.md.

The high-level flow is:

1. Navigate to the article's edit URL in Zendesk
2. Use the CKEditor JavaScript API to get the current content, apply the replacement, and set the new content
3. Click Save, then open the dropdown and click Publish (not just Save)
4. Confirm the article shows "Published this minute" or equivalent

After all articles are updated, tell the user: which articles were updated, a brief summary of what changed in each, and that they're now live.

Edge cases and tips

Finding the edit URL: When viewing an article on the public HC while logged in as an admin, there's an "Edit article" link at the top that goes to https://[subdomain].zendesk.com/knowledge/articles/[id]/en-us?brand_id=.... Use that link to open the editor.

Smart quotes: Zendesk stores content with Unicode smart quotes (\u2019 for apostrophes, \u201C/\u201D for double quotes). When doing string matching on article body content fetched via the API, use Unicode escapes rather than straight ASCII apostrophes or you'll get false negatives.

Drafts vs Published: In Zendesk's new editor, clicking "Save" saves a draft but does NOT publish it. You must open the dropdown next to the Save button and click "Publish". After publishing, the status indicator at the top of the editor should change to "Published this minute" (or "Published just now").

Articles with multiple issues: If one article has two separate sections that need updating, apply both changes before clicking Publish — don't publish after each individual change.

Internal-only articles: Articles marked "Only visible to agents and admins" are updated the same way — the edit flow is identical. These are the bot knowledge base / internal agent articles.

Content not found: If you can't find the old text in the article (maybe it was already updated or the wording differs), tell the user and show them the current content of that section so they can decide.

Reference files

• references/zendesk-editor.md — Technical details for editing Zendesk articles via the CKEditor JavaScript API in Claude in Chrome. Read this before Step 5.