AI & research · One purpose, multiple implementations
receive schedule events and list channelmessage microsoft teams and team member weekly report agent
Adapt the published “receive schedule events and list channelmessage microsoft teams and team member weekly report agent” workflow to other implementations while preserving its documented behavior.
The source contains 12 executable nodes and 11 connections. This draft is derived from the n8n export; it needs a human-reviewed purpose, input/output contract, and behavioral tests before a port can claim equivalence.
Open agent files on GitHub ↗Shared workflow
This initial Mermaid diagram shows observed connections from the n8n source, including model and tool dependencies. Unresolved connections are listed under Evidence. It is a starting point for the shared design; it does not execute the agent or establish correctness.
Rendering the workflow diagram…
Read the Mermaid source
flowchart LR n0["Schedule Trigger"] n1["Fetch Latest Channel Messages"] n2["OpenAI Chat Model"] n3["Team Member Weekly Report Agent"] n4["Merge Report With User Data"] n5["OpenAI Chat Model1"] n6["Reports to Single List"] n7["Team Weekly Report Agent"] n8["Markdown to HTML"] n9["Send Report to Channel"] n10["Group Messages By UserId"] n11["Groups to Items"] n11 -->|"main out 0 to in 0"| n3 n8 -->|"main out 0 to in 0"| n9 n0 -->|"main out 0 to in 0"| n1 n2 -->|"ai_languageModel out 0 to in 0"| n3 n5 -->|"ai_languageModel out 0 to in 0"| n7 n6 -->|"main out 0 to in 0"| n7 n10 -->|"main out 0 to in 0"| n11 n7 -->|"main out 0 to in 0"| n8 n4 -->|"main out 0 to in 0"| n6 n1 -->|"main out 0 to in 0"| n10 n3 -->|"main out 0 to in 0"| n4
Implementations
Each implementation shares the agent’s purpose. Available source, planned ports, and verified results are labeled separately.
n8n
Source available · not runtime-tested
Read setup and source ↗Inspect the n8n canvas and download JSON →Build or operate with an assistant
Each prompt includes separate build and operating instructions tailored to this agent. They are untested instructions, not working implementations. Check the chosen product’s actual capabilities before using it.
Evidence and remaining work
The bulk collection has publication checks, not live-service testing. Diagrams and prompts are documentation. A port needs reviewed schemas, fixtures, actual execution results, and explicit limits before claiming equivalent behavior.
- Define input/output schemas and expected outputs.
- Review source expressions, external actions, and failure behavior.
- Determine whether model judgment is required or deterministic rules suffice.
Curated by Nik Bear Brown. Preserve each implementation’s original attribution and license. These source templates are separate from the audited Claude directory.