Information flow atlas
Your systems, read with permission.
Robin works through provider-native adapters behind a uniform, organization-authorized tool surface. Connection does not imply unrestricted access, identical provider breadth or automatic write permission.
Gmail
Drive
Slack
Notion
Asana
Jira
HubSpot
HiBobNormalize bounded results.
Connect evidence.
Preserve source identity.
Google WorkspaceGmail · Google Drive · Google Sheets · Google Calendar
Communication and knowledgeSlack · Notion
Work managementmonday.com · Asana · Jira · ClickUp
CRMHubSpot · Salesforce
People directoryHiBob
Provider-native, organization-authorized
Robin works through provider-native adapters behind a uniform, organization-authorized tool surface. A connected provider does not create unrestricted access, identical capability across systems or automatic permission to write.
Current connected-system families
The reviewed public support set spans Google Workspace, communication and knowledge, work management, CRM and the HiBob people directory. Each family is presented as product support, not as evidence that every visitor’s organization has configured every connection.
- Google Workspace: Gmail, Google Drive, Google Sheets, Google Calendar
- Communication and knowledge: Slack, Notion
- Work management: monday.com, Asana, Jira, ClickUp
- CRM: HubSpot, Salesforce
- People directory: HiBob
Search broadly enough, read exactly
Provider behavior is native and uneven. Robin searches bounded candidates, then reads exact authorized records with provider-specific identity, pagination, truncation and freshness semantics. It does not claim a universal query language or unlimited cross-provider search.
Read and write are separate boundaries
Project setup uses provider reads plus Robin-owned Wiki and roadmap tools; it does not write to external systems. Elsewhere, only supported external action types can be prepared, and execution requires the applicable human approval and authorization check.
Bounded results, protected secrets
Source adapters normalize bounded provider results for the task at hand, while connected credentials remain a server-side concern. Some source-derived content may become grounded Robin knowledge, so the public promise is controlled handling rather than an absolute claim that nothing is retained.
Availability belongs to the organization
Connector capability, scopes and deployment configuration may vary. The authenticated Integrations surface is the operational authority for a specific organization; this public document describes supported product families and their boundaries.
Continue through permission
Review how Robin protects identity, tenant and action boundaries, see how authorized context becomes execution, or discuss a design partnership for a bounded workflow and an agreed connection scope.