Monitor meetings, email, and repos
Stop waiting to be asked for a meeting recap or an inbox sweep. An AI teammate that watches Lark meetings, Gmail, and GitHub on its own, routes what it finds to the right place, and reports what's still open at day's end.
This teammate doesn't just summarize. It decides where each finding goes, and the routing rule matters as much as the summary. Meeting notes go by DM to the owner, never a group channel. An R&D bug or feature request becomes a real Helio Task; a GTM or ops item gets noted as a to-do in the recap, no Task created. A broken tool connection or permission error gets surfaced in the daily digest and waits for a human; it doesn't retry forever on its own. System notifications and noise emails get ignored outright; they never interrupt you. Set the rules once, and it keeps applying them without being asked again.
Copy this prompt to start your first task:
What is this workflow?
This is an AI teammate that watches Lark/Feishu meetings, Gmail, and GitHub on its own, instead of waiting to be asked for a recap or an inbox sweep. After each meeting, it DMs a structured recap — decisions, to-dos, background, open disagreements — straight to the person who owns the follow-up, never a group channel. It also triages your inbox, holding reply drafts for your approval before anything sends, while surfacing payment items that need action and SEO notices worth a glance, and ignoring the noise. At day's end, a nightly digest reports what's still unresolved — a stalled reply, an expiring token, a broken connection — and keeps surfacing it until it's actually closed, not just once.
How to use this workflow
Hire a GTM teammate, then write the bio to match this job, not the generic template
Open AI Teammates in the sidebar, click Hire AI Teammate, and pick the GTM Lead template. Its default bio is about coordinating campaign content. Replace it on the Profile step so the teammate starts out already knowing this is an information-ops role, not content production:
Confirm the name and click Create teammate. They land in their own channel, which is where you'll send everything below. More on hiring →
Connect in the order the sources actually matter
Meetings are the primary source, so get Lark/Feishu set up first, then Gmail, then GitHub last. The three connect differently. Lark/Feishu is not a standard OAuth card in the Tools tab: it connects through a self-built app on the Feishu open platform, a one-time admin-level setup rather than a sign-in-and-approve flow. Gmail is the simple case — a per-teammate OAuth connection from this teammate's own Tools tab: open the connection, sign in, approve. GitHub is a two-layer setup: a workspace admin installs the Helio GitHub App once for the organization from Settings → Integrations, and only after that can this teammate be granted the specific repositories it should watch (like the one holding user-interview docs) from its own Tools tab. Connect your tools →
Give it a real meeting, not a test transcript
Point it at an actual recording and check that it comes back in the SOP's shape (decisions, to-dos, background, open disagreements) sent as a DM, not posted to the group:
Set the routing rules once: this is what makes it trustworthy, not just fast
A recap is only half the job; where each finding goes matters as much as what it says. Give it the table once and it applies it every time without re-asking:
| Finding | Routing |
|---|---|
| Meeting notes | DM to the owner, never a group channel |
| R&D bug or feature request | Create a real Helio Task |
| GTM or operations item | Note it as a to-do in the recap, no Task |
| Broken tool connection or permission error | Surface in the daily digest, wait for a human |
| System notification or noise email | Ignore, never interrupt you for it |
Turn the nightly digest into an automation
Instead of remembering to ask for a status check every evening, open Automations in the sidebar and click Create via Chat. On Home, choose this teammate and send the prefilled scheduled-task starter. When the interview asks what to schedule, answer with the recurring job below:
Only sending an email reply needs your approval: reading meetings, email, and repo activity, creating a Task, and DMing you a recap or digest all run on their own — drafting and sending an actual reply is the one action that leaves Helio, so it pauses for your sign-off first. See Control for what else pauses for approval.
Tips for Better Results
| Tip | Description |
|---|---|
| Connect sources in priority order | Lark/Feishu needs a one-time admin setup on the Feishu open platform before anything else works; get that done first, then Gmail's simple per-teammate OAuth, then GitHub's two-layer install — a workspace admin adds the GitHub App org-wide, then you grant this teammate specific repos. |
| Test on a real recording, not a placeholder | Point it at an actual call before trusting the recap's shape (decisions, to-dos, background, disagreements) and the DM-not-group routing. |
| Hand over the routing table once, verbatim | Meeting notes, R&D bugs, GTM items, broken connections, and noise each go somewhere different — give it the full table so it isn't guessing case by case. |
| Turn the nightly check into an Automation | Don't rely on remembering to ask every evening. Set the digest up once under Automations so it fires at a fixed time on its own. |
Common Questions
Team & Personal Productivity
Back to the Team & Personal Productivity use case overview.
Source and screen candidates
Turn a job description into a scored candidate shortlist.
Run your company solo with AI
Hire across every function a small company needs.
Plan your day automatically
Scans channel activity for commitments, checks whether today's plan actually fits the hours available, and carries forward anything that slipped.
Triage support tickets
Build a knowledge base once. It answers the routine tickets and escalates anything complex with the context already gathered, never alone.