Supported Integrations
OpsTower supports 34 integrations across twelve categories: analytics, error tracking, payments, logs, databases, ticketing, code, social, advertising, app stores, customer support, and external APIs. This page provides a quick reference for each integration’s authentication method and required credentials.
Integration Reference
Section titled “Integration Reference”| Integration | Category | Auth Method | Key Credentials |
|---|---|---|---|
| PostHog | Analytics | API Key | API key (phx_), Project ID |
| Amplitude | Analytics | OAuth 2.0 | Automatic via OAuth |
| Google Analytics 4 | Analytics | Service Account | JSON key file, Property ID |
| Mixpanel | Analytics | Service Account | Service Account Username, Secret, Project ID |
| Sentry | Error Tracking | Auth Token | Internal Integration token, Organization slug |
| Stripe | Payments | API Key | Restricted API key (rk_live_) |
| Axiom | Logs | API Token | Token (xaat- / xapt-), Dataset |
| Cloudflare Logging | Logs | API Token | API token, Account ID |
| Google Cloud Logging | Logs | Service Account | JSON key file, Project ID |
| AWS CloudWatch | Logs | IAM Credentials | Access Key, Secret Key, Region |
| MongoDB | Database | Connection String | Connection string (mongodb:// or mongodb+srv://) |
| ClickHouse | Database | Username / Password | URL, Username, Password, Database |
| Cloudflare D1 | Database | API Token | API token, Account ID, Database ID |
| Supabase | Database | JWT | Project URL, Service Role Key |
| Generic SQL | Database | Connection String | Connection string (postgres:// or mysql://) |
| AWS DynamoDB | Database | IAM Credentials | Access Key, Secret Key, Region |
| Google Firestore | Database | Service Account | JSON key file, Project ID |
| Linear | Ticketing | API Key | Personal API key (lin_api_) |
| GitHub | Code | PAT | Personal Access Token |
| Paddle | Payments | API Key | API key (pdl_live_ or pdl_sdbx_), Environment |
| Chargebee | Payments | API Key | Site subdomain, Read-only API key |
| Braintree | Payments | API Key | Merchant ID, Public Key, Private Key, Environment |
| Jira Cloud | Ticketing | OAuth 2.0 (PKCE) | Automatic via OAuth, Cloud ID |
| Bitbucket Cloud | Code | OAuth 2.0 (PKCE) | Automatic via OAuth, Workspace slug |
| GitLab | Code | OAuth 2.0 (PKCE) | Automatic via OAuth, Username |
| X (Twitter) | Social | OAuth 2.0 (PKCE) | Automatic via OAuth |
| Social | OAuth 2.0 | Automatic via OAuth | |
| Facebook & Instagram | Social | OAuth 2.0 | Automatic via OAuth (Page Access Token) |
| Meta Ads | Advertising | OAuth 2.0 | Automatic via OAuth, Ad Account ID |
| Google Ads | Advertising | OAuth 2.0 | Automatic via OAuth, Customer ID |
| App Store Connect | App Store | API Key (JWT) | Issuer ID, Key ID, Private Key (.p8) |
| Intercom | Support | OAuth 2.0 | Automatic via OAuth |
| Zendesk | Support | OAuth 2.0 (PKCE) | Subdomain, OAuth Client Identifier, Client Secret |
| External API | External API | Flexible | Base URL + Bearer / API Key / Basic Auth / Query Param / None |
Credential Security
Section titled “Credential Security”All credentials are encrypted at rest using AES-GCM. Credentials are decrypted only at the time of use and are never exposed in logs, API responses, or the user interface after initial entry.
Category Overview
Section titled “Category Overview”Analytics
Section titled “Analytics”Analytics integrations connect OpsTower to your product analytics platforms. They power both scheduled reports and real-time agent queries during chat sessions.
Log integrations give agents access to application and infrastructure logs. Agents can search, filter, and analyze log data to help with debugging and incident investigation.
Databases
Section titled “Databases”Database integrations allow agents to query your data stores directly. Agents can run read-only queries to retrieve data relevant to your questions.
Error Tracking
Section titled “Error Tracking”Error tracking integrations give agents access to grouped error data with stack traces, frequency trends, and project-level stats. Agents can surface overnight error spikes and correlate them with other signals.
Payments
Section titled “Payments”Payment integrations connect agents to your revenue and subscription data. Agents can query subscriptions, charges, invoices, and balance transactions to include financial metrics in daily reports.
Ticketing
Section titled “Ticketing”Ticketing integrations let agents search, view, and create issues in your project management tools. They enable automated ticket creation from systems operations reports, so issues discovered overnight are tracked before your team starts the day.
Code integrations provide agents with access to your source code repositories. Agents can browse files, search code, and review commit history to correlate code changes with observed issues.
Social
Section titled “Social”Social integrations connect agents to your social media accounts for engagement metrics, post performance, and audience insights. Agents can correlate social activity with product analytics to attribute traffic spikes and measure content impact.
Advertising
Section titled “Advertising”Advertising integrations connect agents to your ad platforms for campaign performance, spend analytics, and audience breakdowns. Agents can correlate paid acquisition with product metrics to calculate true CAC and ROAS.
App Stores
Section titled “App Stores”App store integrations connect agents to mobile app distribution platforms. Agents can query app reviews, ratings, and metadata to surface user sentiment, track review trends, and correlate app store feedback with product analytics.
Customer Support
Section titled “Customer Support”Customer support integrations give agents access to support tickets, conversations, CSAT ratings, help center articles, and performance metrics. Agents can correlate customer issues with product analytics and operational signals to surface patterns and drive faster resolution.
External APIs
Section titled “External APIs”External API connections let you integrate any REST API that OpsTower does not have a dedicated integration for. Provide a base URL and authentication credentials, and agents can make HTTP requests to query data from any service – internal microservices, third-party SaaS platforms, or partner data feeds. All requests include SSRF protection and header sanitization.