> H2G2 Federated Wiki + Microsoft Teams Integration Pilot This document outlines the architecture and cost model for integrating Microsoft Teams Chat into the federated wiki Guide Writing Workflow for the H2G2 Community, using self-hosted automation tools and community resources.
## Project Context This pilot project is a self-contained, community-financed experiment in integrating Microsoft Teams text chat with Federated Wiki writing. The aim is to support live collaboration by capturing and transforming selected chat content into wiki pages in real time.
All infrastructure will be hosted at the Vaudeville (London) Embassy using an affordable Hitchhiker Homelab setup that can easily be setup by any community at home or in a community centre. The integration will rely on the open-source automation platform n8n to bridge between Teams and Federated Wiki.
# Architectural Overview - **Microsoft Teams**: The H2G2 community's existing communication platform. - **n8n (Self-hosted)**: An open-source automation tool used to monitor Teams chat, extract relevant content, and transform it into wiki-compatible formats. - **Federated Wiki**: The collaborative guide-writing environment where new or updated pages will appear based on chat activity. - **Raspberry Pi 5 (HomeLab)**: Host for n8n and supporting services, using dynamic DNS and a reverse proxy for external access.
# Integration Flow 1. n8n connects to Microsoft Teams using Microsoft Graph API, authorized via an Azure App Registration tied to the H2G2 Teams workspace. 2. n8n listens for specific triggers in chat (e.g., messages prefixed with `!wiki`) or compiles message digests on a timer. 3. Content is parsed and formatted into Federated Wiki-compatible JSON or Markdown. 4. The formatted content is pushed to the Federated Wiki instance via file write or HTTP API.
## Cost Model This pilot is designed to be sustainable within a low-cost, community-supported model.
### Self-hosted n8n - Hosted on Raspberry Pi 5 with Docker. - Uses dynamic DNS (e.g., DuckDNS or Cloudflare Tunnel). - No license or execution limits. - No recurring infrastructure fees.
### Microsoft Teams Access - Utilizes the H2G2 community’s existing Microsoft 365 accounts. - No additional licensing required. - Azure App Registration for Graph API is free.
### Estimated Operating Costs | Resource | Cost | |---------------------------|------------------------| | Raspberry Pi electricity | Negligible (~£5/year) | | Domain/DNS (if used) | Free or low (~£5/year)| | Microsoft 365 licenses | Already provisioned | | n8n (self-hosted) | Free | | Community contributions | Based on £42/year members |
## Financial Model The pilot is fully supported by the H2G2 community under an intentional model of sustainability. All recurring costs are minimal and collectively manageable. The symbolic £42/year membership serves as both a cultural homage and a financial scaffold for experiments such as this.
## Conclusion This project bridges asynchronous wiki writing and real-time community conversation in a durable, low-cost, and privacy-respecting architecture. It leverages existing infrastructure, free and open-source tools, and the collective energy of the H2G2 community to pilot a new form of collaborative guide-building. # See