Sources
Data Sources
Connect Stripe, Supabase, and more to alice — query production data from Slack with OAuth connections
Data Sources
Supported Sources
| Source | Data Available | Connection | Actions |
|---|---|---|---|
| Stripe | Revenue, customers, subscriptions, payments, disputes, trials | OAuth (one click) | Tag customer, add note |
| Supabase | Any table in your Postgres database | OAuth + project picker | -- |
Coming Soon
| Source | Data | Status |
|---|---|---|
| PostHog | Product analytics, feature adoption, session data | Phase 2 |
| Crisp / Intercom | Support tickets, conversations | Phase 2 |
| Linear | Engineering tickets, sprints | Phase 3 |
| HubSpot | CRM, deals, contacts | Phase 3 |
| GitHub | Deployments, pull requests | Phase 3 |
Source Limits by Plan
| Plan | Max Sources |
|---|---|
| Free Free | 1 |
| Pro Pro | 3 |
| Business Business | Unlimited |
Combined Queries
The real power of alice is combining data across sources. When you have both Stripe and Supabase connected, you can build combined queries that join revenue data with application data in a single skill. Pro
Example: identify customers with failed payments and low login activity -- data that lives in two different systems.
/alice churn-risk
3 accounts at high churn risk:
- jane@acme.com — Payment failed, no login 18 days
[Tag in Stripe] [Send DM]
- bob@startup.io — Card expiring, 2 sessions this month
[Send reminder] [Tag in Stripe]
Data from Stripe + SupabaseHow Sources Work
- OAuth authorization -- You grant alice read-only access to the service
- Schema discovery -- alice reads your data schema to power the Visual Builder and AI generation
- Credential storage -- Encrypted OAuth tokens stored with AES-256-GCM
- Real-time queries -- Skills execute against the source API/database at runtime (no sync, no warehouse)
See Security for details on credential handling and encryption.
Was this page helpful?