CUSTOMER SUPPORT
Auto-draft a README troubleshooting entry from clustered Intercom conversations
Watches resolved Intercom conversations, clusters recurring issues over a rolling window, and when a problem crosses a frequency threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule over rolling 7-day window
- ActionFetch resolved conversations from IntercomIntercom
- ActionCluster conversations by root cause and count occurrencesOpenAI
- LogicKeep only clusters above recurrence threshold
- ActionDraft titled troubleshooting section per clusterOpenAI
- OutputCreate unpublished README draft for editor reviewReadMe
What it does
It turns repeat support pain into documentation. The workflow groups recently resolved Intercom conversations by root cause, and when the same issue shows up often enough to matter, it writes a clean troubleshooting entry and stages it in README as an unpublished draft for a human to approve.
When to use it
Use it when the same questions keep landing in your inbox and your docs never quite catch up. Good for support teams who want self-serve deflection without manually mining tickets every week.
How it works
- 1A schedule fires on a rolling window (e.g. nightly over the last 7 days).
- 2It pulls resolved conversations from Intercom for that window.
- 3An OpenAI step clusters them by underlying issue and counts occurrences.
- 4A logic gate keeps only clusters above the recurrence threshold.
- 5For each qualifying cluster, OpenAI drafts a titled troubleshooting section with symptoms, cause, and fix steps.
- 6The draft is created as an unpublished page in README, ready for editor review.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 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
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.
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.
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.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.