Integrations
Integrations connect external services to a user’s profile, allowing the AI to access relevant data like calendars, emails, and custom APIs. This enables contextual responses based on real-time information.How Integrations Work
During conversations, the AI can query connected integrations to provide contextual responses:- “What’s on my calendar today?” → Queries Google Calendar
- “Did I get any emails from Sarah?” → Queries Gmail
- “What’s my order status?” → Queries custom API
Available Integrations
| Integration | Description | Data Access |
|---|---|---|
| Google Calendar | Calendar events | Read events, create events |
| Gmail | Email messages | Read emails, search |
| Microsoft 365 | Calendar & email | Read events, emails |
| Notion | Notes & databases | Read pages, query databases |
| Linear | Issue tracking | Read issues, projects |
| Custom Webhook | Your own APIs | Whatever you expose |
List User Integrations
Connect an Integration
OAuth Integrations
For OAuth-based integrations (Google, Microsoft, etc.), initiate the connection flow:authorization_url. After they authorize, they’ll be redirected to your redirect_url with an authorization code.
Complete OAuth Connection
Webhook Integration
For custom integrations, configure a webhook:Get Integration Details
Update Integration
Update integration settings:Disconnect Integration
Integration Permissions
Control which personalities can access which integrations:Using Integrations in Conversations
Enable integration access in the conversation pipeline:Query an Integration Directly
Test integration queries outside of a conversation:Refresh Integration Tokens
For OAuth integrations, tokens are refreshed automatically. To force a refresh:Integration Health
Check if integrations are working:healthy- Working normallydegraded- Experiencing issuesdisconnected- Needs reconnectionexpired- Token expired, needs reauthorization
Webhook Integration Details
When the AI queries your webhook integration, Spike sends:Privacy & Security
Data Minimization
Integrations only access data when queried during conversations. Spike does not store integration data - it’s fetched in real-time and discarded after the conversation.User Consent
Users must explicitly authorize each integration. They can revoke access at any time through disconnection.Token Security
- OAuth tokens are encrypted at rest
- Refresh tokens are used to maintain access without re-authorization
- Tokens are scoped to minimum necessary permissions

