CUSTOMER SUPPORT
Re-Validate Macros When a Help-Center Article Changes
When a Confluence help-center article is published or updated, immediately checks which Zendesk macros cite it and flags any whose canned answer now contradicts the new version.
How it runs
The automated pipeline, trigger to output.
- TriggerConfluence article published or updatedConfluence
- ActionRead updated article body and URLConfluence
- ActionFind Zendesk macros referencing this articleZendesk
- LogicExit if no macros reference the article
- ActionLLM compares each macro to the new articleOpenAI
- OutputAlert author and support-ops in SlackSlack
What it does
Instead of waiting for a nightly sweep, this workflow reacts the moment a help-center article changes. A Confluence publish event triggers a targeted recheck: it finds only the macros tied to that specific article and verifies each one against the freshly published text, so contradictions surface within minutes of a doc edit.
When to use it
Use it when documentation changes are the leading cause of macro drift and you want fast feedback to the writer who just made the edit. Ideal for teams practicing docs-as-source-of-truth, where a policy change should propagate to canned replies the same day.
How it works
- 1A Confluence webhook fires on article publish or update.
- 2Read the updated article body and identify its help-center URL.
- 3Query Zendesk for macros that reference that URL or article ID.
- 4If no macros reference the article, the run exits quietly.
- 5The LLM compares each matching macro to the new article text and flags contradictions with specifics.
- 6Notify the editing author and support-ops in Slack listing every macro that now needs a rewrite.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.