CUSTOMER SUPPORT
Append an FAQ answer to README when an agent tags an Intercom conversation
When a support agent closes an Intercom conversation with a 'doc-this' tag, it summarizes the question and resolution and appends a Q&A block to a chosen README FAQ page.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation tagged 'doc-this'Intercom
- LogicConfirm conversation is closed and tag matches
- ActionFetch full conversation threadIntercom
- ActionDistill into PII-stripped Q&A blockOpenAI
- ActionAppend Q&A to target README FAQ pageReadMe
- OutputPost confirmation note back to IntercomIntercom
What it does
It lets agents promote a single great answer into the docs with one tag. The moment a conversation is tagged for documentation, the workflow extracts the customer's question and the agent's resolution, formats it as a clean Q&A, and appends it to your README FAQ page.
When to use it
Use it when individual agents already know which answers deserve to live in the docs and you want zero-friction capture at close time, rather than a batch review later.
How it works
- 1An Intercom event fires when a conversation is tagged 'doc-this'.
- 2A logic check confirms the conversation is closed and the tag matches.
- 3The full thread is pulled from Intercom.
- 4OpenAI distills it into a concise question and a step-by-step answer, stripping any customer PII.
- 5The new Q&A block is appended to the target README FAQ page.
- 6A confirmation note is posted back to the Intercom conversation so the agent knows it landed.
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.