Integrations
Every connection has a job. You set the limit.
Botable reads from the software that holds your official record, inherits the access model already in place, and returns finished work where your people already operate.
Start with one gap→Connection model
Each connection has a clear job.
Botable works with the source, access model, and daily tools already in place. Read, delivery, and write permissions are defined around the work.
- 01
Systems of record
Botable reads the official version and returns approved updates through the same system when the workflow requires it.
Never: Write a record state nobody released.
Read and update - 02
Identity and access
The connection follows the access model already in place. People see and act only within the permissions defined for the build.
Never: Create a permission tier of its own.
Use existing access - 03
Where work happens
Resolved work returns to the tools people already use, and approved follow-through is recorded where the operation needs it.
Never: Send on anyone's behalf without the review the workflow specifies.
Deliver and record
Identity provider
- Microsoft Entra ID
- Okta
- Active Directory
- Google Workspace
- Ping Identity
- JumpCloud
- OneLogin
- Auth0
- Duo
Standard protocol
- SAML 2.0
- OpenID Connect
- SCIM
- LDAP
Chat and collaboration
- Microsoft Teams
- Slack
- Google Chat
- Webex
- Zoom Team Chat
Email
- Microsoft Outlook
- Exchange Online
- Gmail
Service desk
- ServiceNow
- Workday Help
- Zendesk
- Jira Service Management
- Freshservice
- HaloITSM
All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
Access and ownership
You keep control of the record and the access.
Together, we define what Botable can read, what it can write, who can receive the result, and which decisions stay with your team. Your source records and access decisions remain yours.
Show us where the work starts and where the result belongs.
Bring the system that holds the record and the tool your team actually opens. We will map the read, delivery, approval and write path around them.
Start with one gap