The Macros API (GET /macros and GET /macros/{id}) is a great start, but it is read-only. Please add POST, PUT and DELETE so teams can manage macros programmatically, the same way we already can with Articles, Internal Articles, Content Snippets and Folders.
Why this matters (real numbers from our team)
- Our support team runs ~450 macros. Every change is manual copy-and-paste in Settings > Macros.
- In a recent audit of 427 macros, 261 had at least one issue (typos, broken formatting, invisible characters, duplicates, or text contradicting another macro) and 40 were high priority. We could find all of them, but fixing them means opening macros one by one.
- A single pricing and regulatory change in October meant rewriting 8 macros. After a compliance check, several had to be edited a second time within 24 hours, with the wrong text live in the meantime.
- A payment-provider change forced 3 macros to be edited twice in 16 days (a temporary workaround, then a revert).
- Macros go straight to customers. They should be as easy to version, review and roll out as Help Center articles.
- There is no way to see who edited a macro or what changed, so when a wrong text goes live we can't trace it or roll it back quickly.
What exists today
Articles, Internal Articles, Content Snippets and Folders all support create/update/delete. Macros are the only customer-facing content type we cannot write via the API, and the MCP server doesn't expose them either.
Proposal
- POST /macros, PUT /macros/{id}, DELETE /macros/{id} (or archive).
- Same fields the GET already returns: name, body (accepting the <attribute .../> placeholder format), visible_to / visible_to_team_ids, available_on.
- Nice to have:
1. A draft/published state.
2. Folders or tags for macros.
3. Edit history: who changed a macro, when, and what changed, with the ability to compare versions and restore a previous one (also readable via the API).
Use cases
1. Single source of truth: sync macros from a knowledge base or docs tool.
2. Bulk updates when prices, policies or links change.
3. Automated linting: typos, broken links, duplicate or conflicting macros.
4. A review-and-approve workflow before anything reaches customers.
5. Backup and restore.
If you manage a large macro library too, please upvote and share your use case.
Thank you and best regards!