CUSTOMER SUPPORT
Draft a Google Doc from each resolved Intercom chat and assign a reviewer
When an Intercom conversation is resolved, drafts a polished article into a shared Google Drive folder and creates a Linear review task assigned to the on-duty KB editor.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation resolvedIntercom
- ActionRetrieve transcript and resolution notesIntercom
- LogicSkip chats with no real answer
- ActionDraft publish-ready articleOpenAI
- ActionSave draft as Google DocGoogle Drive
- OutputCreate Linear review task with assigneeLinear
What it does
Produces an editable Google Doc draft from every resolved Intercom conversation and immediately puts it in front of a named reviewer. The article lands in a shared Drive folder while a Linear task tracks its path from draft to published, so nothing stalls unowned.
When to use it
Use it when your editorial process lives in Google Docs and your work is tracked in Linear. Best for teams that want each candidate article to have a clear owner and a visible review status rather than a pile of anonymous drafts.
How it works
- 1An Intercom conversation is resolved, triggering the run.
- 2The flow retrieves the transcript and the agent's resolution notes.
- 3A filter skips chats that were resolved without a real answer (auto-close, wrong-channel, spam).
- 4OpenAI writes a publish-ready article with a title, overview, and numbered steps.
- 5The draft is saved as a Google Doc in the shared "KB Review" Drive folder.
- 6A Linear issue is created in the docs team's review queue, linking the doc and the source conversation and assigning the on-duty editor.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Google DriveDocs, sheets, slides, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.