Integrations
Integrations overview
WePeople connects to the tools your team already uses and turns structured metadata into monitoring events, reports, and SPACE scores. Connectors are OAuth-based modules — no agents on laptops, no surveillance posture.
How connectors work
Each integration is a module under Organization → Integrations. An Admin or Owner authorizes the connector (Slack workspace OAuth, GitHub App install, or Atlassian OAuth for Jira Cloud). WePeople stores encrypted tokens, polls or receives webhooks on a fixed cadence, and writes typed events to the monitoring timeline.
Events are attributed to workers — people or AI agents you explicitly monitor — via linked identities. Unmapped activity is ignored. Monitoring filters use module ids such as slack, github, and jira.
For marketing deep-dives with setup walkthroughs and read / do-not-read matrices, see the integrations hub.
Freshness
Freshness is how often new data lands in WePeople after the upstream tool changes. It is not the same as retention — history length depends on your plan.
- Slack — presence polled every 5 minutes; message and reaction metadata on the same cadence.
- GitHub — repository sync roughly hourly for commits and pull-request lifecycle events.
- Jira — issue transitions via webhooks (near real-time after OAuth setup).
Gaps from upstream outages or revoked tokens appear visibly on the timeline — we do not silently backfill with guesses.
Live today
Three first-party connectors ship today. Each has a product guide below and a marketing detail page with FAQs and demos.
On the roadmap
Additional connectors are planned — calendar, issue trackers, design tools, and agent-assisted editors. They follow the same metadata-only contract as live modules.
- Google Calendar — Factor meetings and focus time into work analysis.
- Linear — Issue lifecycle and throughput for Linear-first teams.
- Cursor — Agent-assisted edits as a human-factor signal, not a score.
- Figma — File activity and design-system touches for design teammates.
Need something sooner? Use the Ingest API to push custom events, or request an integration.
Trust model
Every connector ships with an explicit read / do-not-read list. Tokens are encrypted at rest; only roles with integration management permission can connect or disconnect. See the full trust model and privacy model.