Tencent Meeting + GetNote for Document-Driven Project Management
How to use Tencent Meeting and GetNote to connect meeting notes, project documents, and AI agent execution workflows.
Tencent Meeting + GetNote for Document-Driven Project Management
AuraBaba connects Tencent Meeting and GetNote to close the loop between meetings, documents, tasks, and AI agent execution: humans meet and make decisions, AI agents understand context, decompose tasks, execute, and sync progress back into the task system.
Core idea: documents are the bridge between humans and AI
In traditional project management, documents are usually recording tools. In AI agent project management, documents are also the context source through which AI agents understand the project.
Humans write documents
↓
Documents enter the knowledge base
↓
AI agents read documents and understand project background
↓
AI agents decompose tasks, execute, and report
↓
Execution results and task status flow back to the project system
↓
Humans review, approve, and adjust direction
This means:
- Documents are written for both people and AI agents
- Tasks can naturally emerge from meetings and documents
- Task origin, execution process, and final results are traceable
- Team knowledge accumulates as reusable context
Tencent Meeting: meeting ends, project starts
A meeting-driven workflow typically includes these steps:
Tencent Meeting in progress
↓
Meeting content is recorded and organized
↓
GetNote saves meeting notes and key context
↓
AI agent identifies decisions, action items, and owners
↓
Tasks enter the AuraBaba execution queue
↓
Humans review tasks and results
During meetings, humans focus on discussing direction, making decisions, sparking ideas, and evaluating risks. Recording, organizing, extracting tasks, and syncing status can be handed to AI agents.
GetNote: turning project documents into executable context
GetNote's role in this workflow includes:
- Storing project documents, requirement docs, and meeting notes
- Enabling AI agents to search and understand relevant background
- Linking each task back to specific documents and meeting sources
- Archiving execution results back into the team knowledge base
The key value of being document-driven isn't having humans repeatedly explain project context to AI — it's letting AI agents read the context themselves before executing.
Setup note: Get your Tencent Meeting token from the Tencent Meeting AI Skills Zone and your GetNote Client ID and API Key from the GetNote OpenAPI. Install the corresponding skills from the AuraBaba Skill Marketplace and fill in the credentials as prompted.
Complete workflow
Step 1: Create project documents
Create project documents in GetNote with clear project goals, background, constraints, participants, and current decisions. The clearer the documents, the more stable the AI agent's subsequent task decomposition and execution.
Step 2: Hold project meetings
The team discusses project direction and next steps via Tencent Meeting. After the meeting ends, save the notes to GetNote as part of the project documents.
Step 3: Generate tasks
The AI agent identifies key action items from the meeting notes, creates corresponding tasks, fills in necessary background information, and assigns tasks to human or digital teammates.
Step 4: Execute and track
Assigned AI agents begin executing tasks and update progress on the issue timeline. The project lead monitors status through the board, list, or task detail views.
Step 5: Review and iterate
After completing a task, the AI agent enters review status. A human confirms the result, sends it back for revision if needed, and the cycle continues from the next meeting based on updated documents and task status.
Advantages
More natural task creation
Many tasks originate from meeting discussions and document decisions anyway. Meeting-driven and document-driven workflows let tasks be generated directly from the source, reducing post-meeting manual transcription and entry.
AI agents understand project context better
Once project documents are in the knowledge base, AI agents can read goals, boundaries, historical decisions, and constraints before execution, reducing the cost of repeatedly explaining context.
Team knowledge accumulates continuously
Meeting notes, project documents, task results, and review feedback accumulate over time. New members or new agents can understand the project from this content.
Suitable scenarios
| Scenario | Why it fits |
|---|---|
| Frequent product planning meetings | Tasks can be generated from meeting discussions |
| Many complex requirement docs | AI agents can read full background |
| PM managing multiple projects | Repetitive follow-up and status syncing can be automated |
| Remote or hybrid teams | Documents become the unified information source |
| Exploratory projects | When documents update, AI agents can sync to new directions |
Summary
Tencent Meeting handles discussions, GetNote handles context persistence, and AuraBaba turns context into tasks and execution flows. With all three connected, project management shifts from "manual post-meeting follow-up" to "automatic execution the moment the meeting ends."
