Roadmap#
Nothing on this page is built yet
This page records capabilities that the system is designed for but has not implemented. None of the endpoints described here exist today. As each item ships, it moves off this page and into the real docs (with reachable endpoints and tested behavior).
The architecture is capability-based: each connection method is written once and parameterized by provider. The planned surface is below.
Integration methods (planned)#
| Method | What it will do |
|---|---|
| CSV import | A stateful upload → parse → map users → review → execute wizard for one-time migrations. |
| API-key sync | Store a provider API key once, then pull and sync data on demand. |
| Webhooks | Verify signed provider events and react in real time (with replay protection). |
| App install (OAuth) | Install the TeamBoost app into a workspace/repo instead of handling keys. |
Providers (planned)#
No provider adapters are registered yet. The intended initial set:
- Linear, Jira, Monday, Trello — task managers (CSV / API key / webhooks).
- GitHub, Slack — app-install (OAuth) based.
- Google Calendar — calendar sync.
The supported methods per provider will be published on each provider's page as the adapter lands.
Platform capabilities (planned)#
- Per-provider credential storage — provider API keys, OAuth tokens, and webhook secrets, encrypted at rest and never returned by any endpoint.
- Background jobs (worker) — queued sync/import jobs with status polling
(
queued→running→completed/failed).
Tracking#
Implementation sequencing and status live in the internal ExecPlan under
docs/plans/ — this page is the user-facing summary of where things are headed.