receive schedule events and list channelmessage microsoft teams and team member weekly report agent
Configured with Aggregate, Chain LLM, OpenAI Chat Model, Markdown, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Messaging
- AI & models
- Transform
- Code
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Fetch Latest Channel Messages | Messaging | Microsoft Teams | channelMessage / getAll |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Team Member Weekly Report Agent | AI & models | Chain LLM | See node parameters |
| Merge Report With User Data | Transform | Edit Fields | See node parameters |
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Reports to Single List | Transform | Aggregate | See node parameters |
| Team Weekly Report Agent | AI & models | Chain LLM | See node parameters |
| Markdown to HTML | Transform | Markdown | See node parameters |
| Send Report to Channel | Messaging | Microsoft Teams | channelMessage |
| Group Messages By UserId | Code | Code | See node parameters |
| Groups to Items | Transform | Split Out | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
microsoftTeamsOAuth2ApiopenAiApi
Workflow notes
1. Fetch All Channel Messages from Last Week
1. Fetch All Channel Messages from Last Week
Learn more about the MS Teams node
We'll start by fetching all activity in our team channel over the last 7 days and group them by the message author. We can do this using the MS Teams node. This will give us the raw data to pick apart and analyse for reporting purposes.
2. Generate Activity Reports for Each Team Member
2. Generate Activity Reports for Each Team Member
Learn more about the Basic LLM node
With our summarized threads which are grouped per user, we can aggregate them and give them to the AI again to generate a weekly report for the team member. This could include their wins, challenges, learnings or decisions - it really is up to you as to what the report looks like. A fun part of this output is getting to decide the tone of voice and delivery of the report. Don't be a bore and consider adding some personality and flair!
3. Generate Final Report for Whole Team
3. Generate Final Report for Whole Team
Learn more about the Basic LLM node
In this step, we go one level higher and aggregate all individual team member reports together into a big team report. In this way, the overview can group similar activities and generalise activities in a broader sense. The message output will also be shorter which some may find easier to digest.
4. Post Report on Team Channel (on Monday Morning!)
4. Post Report on Team Channel (on Monday Morning!)
Learn more about the Markdown node
Finally, we can post the weekly report in the team channel. This is a great way to automate quick recaps for the team after the weekend break, get others back on track if they've been away or update client team who may pop in now and again to collaborate.
Try It Out!
Try It Out!
This n8n template lets you summarize individual team member activity on MS Teams for the past week and generates a report.
For remote teams, chat is a crucial communication tool to ensure work gets done but with so many conversations happening at once and in multiple threads, ideas, information and decisions usually live in the moment and get lost just as quickly - and all together forgotten by the weekend!
Using this template, this doesn't have to be the case. Have AI crawl through last week's activity, summarize all messages and replies and generate a casual and snappy report to bring the team back into focus for the current week. A project manager's dream!
How it works
- A scheduled trigger is set to run every Monday at 6am to gather all team channel messages within the last week.
- Messages are grouped by user.
- AI analyses the raw messages and replies to pull out interesting observations and highlights. This is referred to as the individual reports.
- All individual reports are then combined and summarized together into what becomes the team weekly report. This allows understanding of group and similar activities.
- Finally, the team weekly report is posted back to the channel. The timing is important as it should be the first message of the week and ready for the team to glance over coffee.
How to use
- Ideally works best per project and where most of the comms happens on a single channel. Avoid combining channels and instead duplicate this workflow for more channels.
- You may need to filter for specific team members if you want specific team updates.
- Customise the report to suit your organisation, team or the channel. You may prefer to be more formal if clients or external stakeholders are also present.
Requirements
- MS Teams for chat platform
- OpenAI for LLM
Customising this workflow
- If the teams channel is busy enough already, consider posting the final report to email.
- Pull in project metrics to include in your report. As extra context, it may be interesting to tie the messages to production performance.
- Use an AI Agent to query for knowledgebase or tickets relevant to the messages. This may be useful for attaching links or references to add context.
Need Help?
Join the Discord or ask in the Forum!
Happy Hacking!
receive schedule events and list channelmessage microsoft teams and team member weekly report agent
receive schedule events and list channelmessage microsoft teams and team member weekly report agent
Purpose and structure
This folder contains the receive schedule events and list channelmessage microsoft teams and team member weekly report agent workflow. Its executable nodes use aggregate, chainLlm, code, lmChatOpenAi, markdown, microsoftTeams, scheduleTrigger, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/0923_Splitout_Code_Send_Scheduled.json MIT; preserve source notices.