CUSTOMER SUPPORT
Confluence Archive Event to Affected Zendesk Macro Alert
Triggers the moment a Confluence page is archived or deprecated, finds every Zendesk macro that links to it.
How it runs
The automated pipeline, trigger to output.
- TriggerConfluence page archived or deprecatedConfluence
- ActionCapture affected page ID and URL
- ActionSearch macros referencing that pageZendesk
- LogicExit if no macros reference it
- OutputAlert support ops in SlackSlack
What it does
When a documentation owner archives or deprecates a Confluence page, this immediately reverse-looks-up which Zendesk macros still reference that exact page and alerts support ops in real time. It closes the gap between docs changing and macros pointing at dead content.
When to use it
Use it when your docs team and support team move at different speeds. The day a page is retired is exactly when its links go stale everywhere else — this catches that the same day instead of weeks later in a periodic audit.
How it works
- 1A Confluence webhook fires on a page archive or deprecation event.
- 2Capture the affected page ID and URL from the event payload.
- 3Search the Zendesk macro library for any macro body containing that page URL or ID.
- 4Branch: if no macros reference it, exit quietly; otherwise continue.
- 5Post a Slack alert to the support ops channel naming the retired page and every macro that must be updated, with direct edit links.
Set it up
What you configure once, before turning it on.
- 1Connect ConfluenceSpaces, pages, blueprints.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.