CUSTOMER SUPPORT
Agent triages emailed support answers and drafts help docs to Google Drive
An agent reviews resolved Gmail support threads, decides which freehand answers deserve a help-center article, drafts them, and saves the docs to a Google Drive folder…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled review of resolved email threads
- ActionAgent reads each Gmail support threadGmail
- LogicAgent decides which answers merit a doc
- ActionAgent drafts articles for selected threadsOpenAI
- ActionSave drafts to shared Drive folderGoogle Drive
- OutputPost decision digest to SlackSlack
What it does
Runs an agent over resolved support emails in a shared Gmail inbox. Rather than a fixed rule, the agent reads each thread, judges whether the answer is reusable and not already documented, and decides on its own which ones are worth turning into help-center content. For the ones it picks, it writes full draft docs, saves them to a shared Google Drive folder, and posts a digest of its decisions to Slack.
When to use it
Use it when support happens over email and the line between a one-off reply and a documentable answer needs judgment, not a hard rule. Good for smaller teams without a formal ticketing system.
How it works
- 1A scheduled run hands the agent the recently resolved support threads.
- 2The agent reads each Gmail thread and assesses whether the answer is reusable, generalizable, and undocumented.
- 3It selects the threads that merit a help-center article and skips one-offs.
- 4For each selected thread, the agent drafts a complete article with title, audience, and steps.
- 5It saves each draft as a document in the shared Google Drive folder.
- 6It posts a Slack summary of what it documented and what it skipped, with reasons.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Google DriveDocs, sheets, slides, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.
