Providers
Bring the places you communicate into Bevel.
Every provider exposes different capabilities through its API, and Bevel tells you exactly what each connection can do. Where support depends on a provider's approval, we say so. Where there's no legitimate way to integrate, we say that too.
Support matrix
Where Bevel connects.
Gmail
PlannedFirst integration target. Official Google APIs with OAuth; Google's app verification is required before the public beta.
Outlook (Microsoft)
PlannedFirst integration target alongside Gmail. Official Microsoft Graph API with OAuth and app registration.
Slack
Requires provider approvalPlanned, subject to Slack's platform terms and app review.
Instagram
Requires provider approvalProfessional (business and creator) accounts only, via official Meta APIs. Requires Meta app approval.
WhatsApp Business
Requires provider approvalWhatsApp Business Platform (Cloud API) only. Personal WhatsApp accounts are not supported.
LinkedIn
Not supportedLinkedIn's personal inbox has no official API. We will not scrape or automate the site, so this is not on the roadmap.
Generic IMAP
PlannedStandards-based email accounts, after the first integrations land.
Provider policy
The rules we play by.
Official APIs only
Every connector is built on the provider's published, documented APIs with proper OAuth consent. If an official API doesn't exist, the provider is listed as not supported.
No scraping. Ever.
We do not scrape web interfaces, automate browsers, or extract cookies and session tokens — for any provider, in any circumstances.
Capability differences are documented
Providers expose different features through their APIs. Each connector documents exactly what it can and cannot do, in the app and on this page, rather than papering over the gaps.
Open source doesn't bypass approval
Parts of the connector layer may be open source. That does not exempt anyone — including us — from a provider's terms, app review, or OAuth verification. Connectors ship only where the provider's rules allow.