Work Context Integrations connect the tools where work already happens to 15Five AI, so Agents can ground their insights in real work activity instead of self-reported updates alone.
This article explains what Work Context Integrations are and where to set them up. For HRIS, SSO, or SCIM integrations, see Integrations & Identity: Overview.
In this article
- What Work Context Integrations do
- How access and privacy work
- Where to connect and manage them
Access and Availability
- Company Admins, HR Admins, and IT Admins can connect or assign a Work Context Integration
- Requires access to Agents Hub
- Available in the Perform and Total Platform pricing packages
Availability varies by integration. The Integrations tab in Agents Hub shows the current status of each one, including any that are still coming soon.
Feature Structure
Work Context Integrations are managed from Agents Hub > Integrations, where they are grouped by category. Each integration has its own detail drawer covering what it enables, what data is used, the permissions it requests, and any plan requirements.
Work Context Integrations are separate from platform integrations such as HRIS, SSO, and SCIM, which are configured elsewhere and cover identity and provisioning rather than work activity.
Supported integrations
The following integrations are available. Availability and setup requirements vary by integration, so check the Integrations tab in Agents Hub for the current status of each one. Each article covers that integration's own permissions, synced data, and backfill window.
- Slack
- Microsoft Teams
- Granola
- Google Calendar
- Microsoft Outlook
- Jira
- Asana
- Linear
- GitHub
- Google Drive
- Microsoft OneDrive
- Notion
- Salesforce
- HubSpot
- Zendesk
- Claude.ai
- Cursor
- OpenAI Codex
How access works
Each integration reads only what the connected account, API key, or approved source permissions allow. Insights stay permission-aware, so people only see insights drawn from information they already have access to in the source tool. Data from private channels, spaces, or restricted projects is not surfaced to someone who is not already part of them.
What You Can Do
Set Up
Manage
Understand the context layer
Common Issues
Key Rules
- Setup requirements, plan requirements, and available data differ by integration. Review the integration's detail drawer before connecting.
- Backfill depth and sync cadence are set per integration, not platform-wide. See the integration's own article for the window that applies to it, and note that actual depth still depends on retention settings and permissions in the source system.
- Connected data is processed to generate insights, patterns, and trends rather than kept as a raw log. The underlying raw content is not retained after 30 days.
- Each integration is read through the permissions granted to the connected identity or API key, and can be revoked from the source tool at any time.
- Insights follow source permissions. Restricted content is never surfaced to people who do not already have access to it.
- Integration availability changes over time. Agents Hub is the source of truth for what is connectable today.