Forty-four integrations. Most teams start with these twenty-four.
Every integration says what Mesa can actually do with it, because read only and write are not the same conversation with your security team. Helpdesks, billing, identity and the developer tools your team already runs.
Zendesk
Helpdesk
Read tickets, write replies, change status, open side conversations.
Jira Service Management
Helpdesk
Read requests, transition issues, add internal comments.
Intercom
Helpdesk
Read conversations, reply, snooze, assign to a teammate.
Gorgias
Helpdesk
Read tickets, reply, tag, and trigger a refund flow.
Salesforce Service Cloud
Helpdesk
Read cases with custom fields, update status and owner.
Slack
Messaging
Post a plan, wait for approval, and report what happened.
Microsoft Teams
Messaging
Same approvals and reports, in a channel or a chat.
Twilio
Messaging
Send an SMS when a customer needs telling and email will not do.
Stripe
Billing
Issue refunds, read invoices, check a customer's payment history.
NetSuite
Billing
Raise invoices from closed jobs and read billing codes.
Shopify
Commerce
Read orders, correct addresses, cancel, and refund.
ShipStation
Commerce
Read carrier flags and reprint labels after a correction.
Okta
Identity
Grant and revoke access with the approval recorded.
Google Workspace
Identity
Group membership, shared drives and mailbox delegation.
Snowflake
Data
Read the tables a playbook needs to decide, never write.
BigQuery
Data
Same read-only access, and your row-level policies still decide what a playbook sees.
Looker
Data
Pull a number into a reply so the customer sees the same figure you do.
ServiceNow
Operations
Read incidents and changes, update state and work notes.
PagerDuty
Operations
Open and resolve incidents when a playbook cannot continue.
Datadog
Monitoring
Read monitors and metrics, group related alerts, and mute a monitor while a fix runs.
Sentry
Monitoring
Read issues and releases, merge duplicates, and name the release that caused them.
GitHub
Developer
Read commits and pull requests, so a ticket arrives with the diff that caused it.
Linear
Developer
Open and update issues, and draft the postmortem when a ticket closes.
Notion
Knowledge
Read runbooks so a playbook follows what your team already wrote.