About Shabe
How does Shabe connect to my tools?
How integrations work, what gets accessed, and what stays in your existing SaaS apps.
Connections, not migration
Shabe connects to the APIs of supported systems (for example HubSpot, Salesforce, Gmail, Google Calendar, LinkedIn, Slack—see the homepage for the current list). Your data stays in those products. Shabe reads (and, on higher tiers, acts) through the permissions you grant.
What “connected” means in practice
- You authorize Shabe once per integration, following each vendor’s OAuth or API security model.
- Shabe uses those credentials to query and summarize information you could already access—without exporting your database to a spreadsheet first.
Security posture
Read-only tiers are designed so teams can get visibility without write risk. When you move to tiers that support actions, your organization defines what agents are allowed to change—aligned with how you already govern CRM and email.
Setup time
Many teams connect core systems in minutes, not multi-week implementation projects—because you’re not re-implementing your CRM; you’re adding a conversational layer.
For product-specific limits and tiers, see Shabe Identify, Shabe Action, and Shabe Enterprise.