Setup and Connections
Integrations Basics
Integrations are the always-on channel of Senses — they're how the world flows into River as entities you can act on.
The two patterns#
- Tool-based — the AI calls the service on demand
- Entity-based — data syncs continuously into your tree
Pick tool-based for lightweight access; pick entity-based when you want continuous reasoning over the data. Most integrations support both.
Setup, in three steps#
- Connect — Settings → Integrations → pick service → OAuth
- Verify — ask SpaceChat to confirm ("show me my last 5 emails")
- Configure — choose what syncs, where it lands
Unblocking common issues#
"I connected, but no data is showing up"#
- Wait a minute — initial sync can take time for active accounts.
- Check the integration status in Settings → Integrations.
- Confirm the entity destination — most integrations sync into a default Group; verify entities are landing there.
"The integration says 'Disconnected'"#
- Token probably expired or password changed. Click Reconnect in the integration card.
- Once reconnected, sync resumes. Already-synced entities are unchanged.
"I want to limit what syncs"#
Most entity-based integrations let you scope:
- Folders (Drive)
- Labels (Gmail)
- Calendars (Calendar)
- Channels (Slack)
- Specific accounts
Configure in the integration's settings panel.
"My AI can't see this integration"#
- Check that the integration is connected (and in the right Dataspace).
- Confirm the relevant Agent has access to its tools (Agent → Tools allowlist).
- For tool-based integrations, the AI may need to be told to use it: "use the Stripe integration to find…"
Choosing the right integration first#
The highest-leverage Senses for most teams:
- Gmail — densest signal
- Google Calendar — second-densest
- Slack — if your team uses it
- Drive — for shared docs
- Browser Extension — for the open web
Connect those five and you have a workspace that feels intelligent within a day.
Custom integrations#
Don't see what you need? Three options:
- MCP server — if one exists for the service (modelcontextprotocol.io)
- Custom App with HTTP tool — see Custom Apps
- Workflow with
http_requestnode — for one-off integrations