Integrations
Learn how to manage integrations with various third-party applications
Overview
Integrations enable SRE.ai to connect to third-party applications via SSO, OAuth, and tokens.
Integrations enable SRE.ai to serve as your intelligent DevOps assistant, monitoring, interpreting, and acting across your stack.
Core capabilities
SRE.ai's Integrations supports six applications:
GItHub
GitLab
Jira
Microsoft Teams
Supabase
How it works
SSO
GitHub utilizes SSO, redirecting the user to the relevant sign-in page when connecting for the first time:
GitHub
Click to learn about connecting GitHub to SRE.ai
From the Command Center welcome screen, click Connect GitHub Account
You'll be redirected to GitHub to install the SRE.ai GitHub App
GitHub will ask: "Where do you want to install SRE.ai GitHub App?"
Select your organization (not your personal account)
On the repository access screen, choose your access scope:
Only select repositories: Choose specific repositories to connect (recommended)
Select at least one repository from the dropdown
Review the permissions SRE.ai is requesting:
Read access to metadata
Read and write access to code, pull requests, and repository hooks
Click Install (or Update access if modifying an existing installation)
You'll be returned to SRE.ai with your GitHub account connected
Important: Select your organization, not your personal account. Clicking your personal account instead of your organization will connect to the wrong context.
OAuth
The following Integrations require OAuth client IDs and OAuth client secrets to connect to SRE.ai:
GitLab
Jira
GitLab
Click to learn about connecting GitLab to SRE.ai
Connecting to GitLab requires three items:
GitLab URL
Use https://gitlab.com for GitLab.com or your self-hosted URL
OAuth Client ID
Read GitLab's documentation to learn about the OAuth Client ID
OAuth Client Secret
Read GitLab's documentation to learn about the OAuth Client Secret
Users who don't yet have OAuth credentials can create the credentials in GitLab's settings.
Jira
Click to learn about connecting Jira to SRE.ai
If your team uses Jira for issue tracking, you can connect it to SRE.ai to link deployments with tickets and automate status updates.
Prerequisites
Access to the Atlassian Developer Console
Permission to create OAuth apps in your Atlassian workspace (admin rights may be required)
Step 1: Create an OAuth App in Atlassian
Go to the Atlassian Developer Console
Log in with your Atlassian account
Click Create → OAuth 2.0 integration
Enter a name for the app (e.g., "SRE-ai")
Agree to the developer terms and click Create
Step 2: Configure Permissions
In your new app, go to Permissions in the left sidebar
Find Jira API and click Add
Configure the following scopes:
read:jira-work— Allows SRE.ai to view issues and projectswrite:jira-work— Allows SRE.ai to create and update issuesmanage:jira-webhook— Allows SRE.ai to receive updates when issues change
Click Save
Step 3: Configure Authorization
Go to Authorization in the left sidebar
Next to "OAuth 2.0 (3LO)", click Add
You'll need to enter a callback URL—get this from SRE.ai:
In SRE.ai, go to Integrations
Click Add Integration → Jira
Copy the callback URL shown in the connection dialog
Paste the callback URL into Atlassian and save
Step 4: Get Your OAuth Credentials
In the Atlassian Developer Console, go to Settings in the left sidebar
Copy your Client ID
Create a new Client Secret and copy it
Step 5: Connect in SRE.ai
In SRE.ai, go to Integrations
Click Add Integration → Jira
Enter your OAuth Client ID and OAuth Client Secret
Click Connect Jira
You'll be redirected to Atlassian to authorize the connection
Select the Atlassian site you want to connect and click Accept
You'll be returned to SRE.ai with Jira connected
Webhook URL
SRE.ai utilizes a Webhook URL to set up its Microsoft Teams integration.
Click to learn about connecting Microsoft Teams to SRE.ai
Connecting to Microsoft Teams requires two items:
Channel Name
Webhook URL
Found in Teams channel → More options (⋯) → Connectors → Incoming Webhook
API Key
SRE.ai utilizes an API Key to set up its Supabase integration.
Click to learn about connecting Supabase to SRE.ai
Connecting to Supabase requires three items:
Integration Name
Project URL
Found in Dashboard → Settings → API
OAuth Client Secret
Read Supabase's documentation to learn about the OAuth Client Secret
Default Schema (Optional)
Use cases
Read SRE.ai's Automations Documentation to learn more about how to coordinate integrations.
Development workflow automation
Trigger:
New commit pushed to GitHub/GitLab
Trigger:
PR opened in GitHub/GitLab
Trigger:
Attempt to merge PR without required approvals
Action:
Parse the commit message for the ticket ID, update the Jira ticket status, add the commit details as a comment, and notify the assigned team in Microsoft Teams
Action:
Create a Jira subtask for code review, assign reviewers based on file paths, post review request in the relevant Teams channel, and log review metadata to Supabase
Action:
Block merge, create a Jira task for security review if needed, send a warning to Teams, log the violation in Supabase for compliance tracking
Issue and project management
Trigger:
New Jira issue created
Trigger:
Jira ticket status changes to "In Progress"
Trigger:
End of sprint (scheduled)
Action:
Analyze issue description, create corresponding GitHub/GitLab issue if code-related, assign to appropriate team, post summary in Teams channel, store routing decision in Supabase for ML training
Action:
Create a feature branch in GitHub/GitLab, update the project board, notify stakeholders in Teams, and log timeline data to Supabase
Action:
Pull completion data from Jira, gather commit stats from GitHub/GitLab, compile a report, post to Teams, and archive metrics in Supabase
Team communication and notifications
Trigger:
Successful pipeline completion in GitHub/GitLab
Trigger:
Critical bug filed in Jira
Trigger:
Scheduled (daily morning)
Action:
Update Jira release version, post deployment summary with changelogs to Teams, query Supabase for affected customers, send targeted notifications
Action:
Create a hotfix branch in GitHub/GitLab, page the on-call engineer via Teams, log the incident timeline in Supabase, and escalate if no response within the SLA
Action:
Query Supabase for the user's tickets, fetch PR status from GitHub/GitLab, pull blockers from Jira, compile a personalized standup summary in Teams DM
Data intelligence and analytics
Trigger:
End of week (scheduled)
Trigger:
Code analysis tool flags issues in GitHub/GitLab
Trigger:
Support ticket closed in Jira
Action:
Aggregate commit frequency from GitHub/GitLab, ticket completion from Jira, analyze patterns, store in Supabase, and generate an insights report in Teams
Action:
Create tech debt tickets in Jira with severity scores, post weekly rollup to Teams, and maintain debt inventory in Supabase
Action:
Check if feature-related, link to GitHub/GitLab issue, survey customer via integrated tool, post feedback summary in Teams, enrich customer profile in Supabase
Security and compliance
Trigger:
Security scan detects CVE in GitHub/GitLab dependencies
Trigger:
Scheduled (quarterly)
Trigger:
PR merged to the production branch
Action:
Create a high-priority Jira security ticket, notify the security team in Teams, log vulnerability details in Supabase, and track the remediation timeline
Action:
Query Supabase for user roles, cross-reference with GitHub/GitLab permissions and Jira projects, generate access review requests in Teams, and log audit trail
Action:
Extract deployment metadata from GitHub/GitLab, update compliance log in Supabase, notify audit team in Teams, attach artifacts to Jira compliance ticket
Customer success operations
Trigger:
New customer record added to Supabase
Trigger:
Feature request logged in support system (via webhook)
Trigger:
Git tag created in GitHub/GitLab
Action:
Create a customer workspace in Jira, provision GitHub/GitLab repositories if needed, set up a Teams channel, schedule kickoff meetings, and initialize the customer dashboard
Action:
Create a Supabase entry, post to Teams for voting, create a Jira epic if the threshold is reached, and link to GitHub/GitLab milestone for planning
Action:
Query Jira for included tickets, fetch customer list from Supabase, generate release notes, distribute via Teams channels, segmented by customer tier
Related Features
Last updated