Distribute Meeting Notes With Teams And ClickUp
After a meeting, this workflow transcribes the recording, summarizes it with AI, posts the recap to Teams.
What it does
Get concise meeting summaries and action items instantly sent to your Microsoft Teams channel while automatic follow-up tasks are created in ClickUp for you. This workflow transcribes your recordings, generates clear recaps with AI, and ensures everyone stays aligned without any manual data entry.
Step by step
- Configure the manual trigger node to accept meeting metadata such as title and date.
- Set up the HTTP request node with the specific endpoint and authentication headers for your transcription service.
- Map the output fields from the Code node directly to the Teams message body and ClickUp task properties.
- Use a Wait node after the HTTP request to poll for completion status if the API is asynchronous.
Where the LLM does the work
- Prompt the LLM in the Code node to extract distinct action items with assigned owners from unstructured notes.
- Instruct the LLM to condense the full transcript into a brief executive summary suitable for a chat message.
- Define the tone and formatting structure of the Teams post to ensure readability across different team members.
Watch out for
Tools that fit
The agent brief
You are helping me build the following AI agent workflow. ## Goal Distribute Meeting Notes With Teams And ClickUp: After a meeting, this workflow transcribes the recording, summarizes it with AI, posts the recap to Teams. ## Specification - What it does: Get concise meeting summaries and action items instantly sent to your Microsoft Teams channel while automatic follow-up tasks are created in ClickUp for you. This workflow transcribes your recordings, generates clear recaps with AI, and ensures everyone stays aligned without any manual data entry. - Trigger: Run manually (Manual · on demand) - Autonomy: Fully hands-off - Expected setup effort: under an hour - Tools/services involved: - n8n: Workflow automation platform - HTTP Request: Transcription service integration - Code: LLM summarization and action item extraction - Microsoft Teams: Posting summaries to channels - ClickUp: Creating action item tasks ## Known pitfalls, handle each one explicitly in your implementation 1. ClickUp task creation will fail if the specified list or space ID does not exist, so verify these IDs before deployment. 2. Teams messages may truncate long summaries, so add a character limit check and link to the full transcript instead. 3. LLM outputs can vary in structure, so parse the JSON response carefully and handle malformed data gracefully. ## Reference implementation https://n8n.io/workflows/12664 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/distribute-meeting-notes-with-teams-and-clickup/ via usecasesforagents.com
Frequently asked questions
Can I use a different Automation Platform than n8n?
Yes. n8n is only the example automation platform in this recipe. The same flow works with Home Assistant. Swap the automation platform connection and keep the rest of the setup as written.
Want this running in your business?
Who it's for
Built for founders and execs who need personal productivity handled without hiring for it.
Ops-IT teams triaging their own internal requests get the same pattern, different queue.