Integrations¶
The Integrations system manages all external service connections that extend Swisper's capabilities. It supports three categories: Email/Calendar (Gmail and Office 365 via OAuth), Notification Channels (Telegram via verification code, Threema via ID), and Data Integrations (WealthOS via API key). All credentials are encrypted at rest via PGPString, and a unified status API aggregates connection state across all integration types.
Key Components¶
| Component | Purpose |
|---|---|
| Email OAuth Flow | Gmail and Office 365 token exchange, encrypted storage, and refresh logic |
| Telegram Registration | 4-digit verification code flow linking a Telegram chat to a Swisper user |
| Threema Registration | Direct Threema ID storage for one-way gateway messaging |
| WealthOS Connection | API key storage for the wealth data integration |
| Integration Status API | Unified GET /integrations/status aggregating state across all types |
| Email Signature Management | Per-account email signature storage (HTML) with CRUD endpoints |
Documentation Sections¶
- Overview — What this module does, integration types, and connection flows
- Architecture — System design, database models, OAuth flows, and design decisions