PlatformLaunch
Connect the tools your teams already use
An application is only useful if it can reach your ticketing system, your document store, and your directory. Cenna ships integrations to all of them — and every integration declares exactly what it may do, so an agent can read one folder and post to one channel and nothing beyond that.
- Integrations
- 98
- Categories
- 11
- Anything with an API
- Connect it yourself
01How it connects
A connection is a grant, not a key
Handing an AI system your Salesforce password is how most of these projects start, and it is why most of them stall in security review. Cenna connects with named scopes instead.
Scoped when connected
Each integration declares what it may do — SharePoint Sites.Read.All, Slack chat:write, DocuSign signature. The grant is visible on the application, not buried in a config file.
Held per application
Contract Hub reaching SharePoint says nothing about what IT Helpdesk can reach. Connections belong to an application and a workspace, not to the whole tenant.
Revocable in a click
Pull a connection and every agent depending on it stops using it immediately. No redeploy, no ticket, no waiting for a release.
Recorded every time
Every call an agent makes through an integration is logged with the run that caused it, so you can answer what touched what and when.
02Catalogue
What Cenna connects to
Search the systems your teams already run, or filter by category. Connecting one is configuration, not a project — you pick it, authorise it, and choose what it may do.
- Okta
- Microsoft Entra ID
- Google Workspace
- OneLogin
- JumpCloud
- Auth0
- Ping Identity
- LDAP
- Slack
- Microsoft Teams
- Gmail
- Microsoft Outlook
- Zoom
- Google Chat
- Twilio
- WhatsApp Business
- ServiceNow
- Jira Service Management
- Zendesk
- Freshservice
- Intercom
- PagerDuty
- Opsgenie
- Front
- Microsoft Intune
- Jamf
- Workday
- BambooHR
- HiBob
- Rippling
- Gusto
- ADP Workforce Now
- SAP SuccessFactors
- Greenhouse
- Lever
- Deel
- NetSuite
- SAP S/4HANA
- Oracle Fusion Cloud
- Coupa
- SAP Concur
- Stripe
- QuickBooks
- Xero
- Chargebee
- Ramp
- Salesforce
- HubSpot
- Microsoft Dynamics 365
- Zoho CRM
- Pipedrive
- Gong
- Outreach
- Clari
- Microsoft SharePoint
- Confluence
- Google Drive
- OneDrive
- Box
- Dropbox
- Notion
- DocuSign
- Adobe Acrobat Sign
- PandaDoc
- Jira
- GitHub
- GitLab
- Bitbucket
- Jenkins
- Datadog
- Grafana
- Sentry
- Linear
- CrowdStrike
- Splunk
- Microsoft Defender
- Wiz
- Qualys
- Tenable
- Proofpoint
- Abnormal Security
- Snowflake
- Databricks
- Google BigQuery
- Amazon Redshift
- PostgreSQL
- MySQL
- MongoDB
- Elasticsearch
- Looker
- Tableau
- Anthropic
- OpenAI
- Google Vertex AI
- Amazon Bedrock
- Azure OpenAI
- Mistral AI
- Meta Llama
03Everything else
Not on the list? It still connects.
The catalogue is what teams ask for most, not a boundary. Anything that speaks REST with OAuth or an API key can be connected and scoped the same way — including the internal service that only your company runs.
REST and OAuth · API keys held as secrets · Same scopes, same audit trail
04FAQ
Common questions
What happens to our credentials?
They are stored as secrets in your own cloud account, alongside the application, and are masked in the console. Cenna orchestrates the connection but never holds your keys in its own infrastructure.
Can an agent reach something we did not approve?
No. An agent can only use integrations attached to its application, and only within the scope that connection was granted. A read scope cannot write, and a connection to one Slack channel is not a connection to your workspace.
How long does connecting a new system take?
The ones in the catalogue are configuration — pick it, authorise it, choose the scope. Something bespoke depends on the API it exposes, and it is the kind of work that fits in a sprint rather than a quarter.
Do integrations count against our AI spend?
No. Integration calls are ordinary API traffic. What shows up in model spend is the reasoning an agent does, which is reported separately from the systems it reaches.
Tell us what your team runs on.
A thirty-minute walkthrough: bring the four or five systems your work actually depends on, and we will show what connecting them looks like and what each agent would be allowed to do.
Get a DemoBuilt for speed. Engineered for control.