CUSTOMER SUPPORT
Capture undocumented Intercom chat answers into a Notion docs queue
When an Intercom conversation closes without a macro or article reference, drafts the missing doc and adds it as a triaged item to a Notion knowledge-base database.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom conversation closedIntercom
- ActionGet transcript and check for macro or articleIntercom
- LogicExit if a saved reply or article was used
- ActionDraft article and propose a categoryOpenAI
- OutputAdd draft row to Notion KB databaseNotion
What it does
Monitors closed Intercom conversations and detects when a teammate answered a customer freehand — no saved reply, no help article inserted. It treats that as a signal the knowledge base is missing something, drafts a candidate doc from the conversation, and files it into a Notion database with a status and suggested category so your docs queue stays organized.
When to use it
Use it when live chat is your front line and good answers vanish into closed threads. Best for teams who manage their knowledge backlog in Notion and want every freehand answer captured as a reviewable draft.
How it works
- 1An Intercom conversation is closed, firing the trigger.
- 2The flow retrieves the conversation transcript and checks for any inserted macro or article link.
- 3If a saved reply or article was used, it exits — nothing new to document.
- 4For freehand answers, OpenAI extracts the core question, drafts an article, and proposes a category.
- 5A new row is created in the Notion knowledge-base database with the draft, category, status of Needs Review, and a link back to the conversation.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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.