CUSTOMER SUPPORT
Sync resolved Intercom workarounds into README and a Notion changelog
When an Intercom conversation closes with a documented workaround, it updates the matching README troubleshooting step and logs the change to a Notion docs changelog for the team.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation closed with resolution noteIntercom
- LogicConfirm note describes a reusable workaround
- ActionMatch issue to existing README sectionOpenAI
- ActionRevise fix steps and write back to READMEReadMe
- OutputAppend change to Notion docs changelogNotion
What it does
It keeps existing troubleshooting docs current as fixes evolve. When an agent resolves an Intercom conversation that contains a better or updated workaround, the workflow finds the matching README section, revises the fix steps, and records the edit in a Notion changelog so the docs team has an audit trail.
When to use it
Use it when your troubleshooting pages already exist but drift out of date as engineering ships fixes and agents discover new workarounds. Best for teams that want maintenance, not just net-new sections.
How it works
- 1An Intercom event fires when a conversation closes carrying a resolution note.
- 2A logic check confirms the note describes a reusable workaround.
- 3OpenAI matches the issue to an existing README troubleshooting section.
- 4If a match is found, OpenAI revises the fix steps to reflect the new workaround.
- 5The updated section is written back to README.
- 6The change is appended to a Notion docs changelog with before/after and source conversation.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect NotionPages, databases, comments.
- 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
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.