Integrations
Learn how to manage integrations with various third-party applications
Overview
Integrations are how SRE.ai connects to the tools beyond Salesforce:
GitHub is the core integration, without it, SRE.ai cannot track branches, trigger automations, or manage pull requests.
The remaining integrations further extend SRE.ai's reach, enabling it to serve as a truly cross-platform DevOps assistant.
Integrations rely on various connection methods such as SSO, OAuth, and API keys.
Core capabilities
SRE.ai's Integrations feature supports five applications:
GitHub
GitLab
Jira
Microsoft Teams
Supabase
Integrations page
If no integrations have been configured yet, the Integrations page displays an empty state with a Connect an integration button. Click it to begin adding your first integration.
Salesforce is not managed here.
To connect a Salesforce org, navigate to Salesforce Orgs instead.
The Integrations page covers third-party tools: GitHub, GitLab, Jira, Microsoft Teams, and Supabase.
Once at least one integration is configured, the page displays a table of your connected integrations.
Setup
SSO
GitHub uses 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
In the Integrations page, click + Add Integration in the top right of the screen and select GitHub
You'll be redirected to GitHub to install the SRE.ai GitHub App
GitHub will ask: "Where do you want to install the 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
Webhook signature verification is enforced.
SRE.ai verifies the signature of every incoming webhook from GitHub using the secret configured for your integration.
Webhook requests with a missing or invalid signature are rejected with a 401 Unauthorized response and will not trigger any pipeline actions.
Ensure the webhook secret in your GitHub repository settings matches the one stored in SRE.ai. A mismatch will cause all webhook events to be rejected.
Viewing enabled repositories:
After connecting, the Integrations table shows your GitHub integration along with the repositories currently enabled for SRE.ai.
You can see at a glance which repos are accessible without leaving the page.
Managing repository access:
To add or remove repositories after the initial setup, use the repository management button in the GitHub row of the Integrations table. This takes you directly to GitHub's repository selection UI.
There's no need to reinstall or fully re-integrate the GitHub App.
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.
Webhook signature verification is enforced.
SRE.ai verifies the signature of every incoming webhook from GitLab using the secret token configured for your integration.
Webhook requests with a missing or invalid X-Gitlab-Token payload are rejected with a 401 Unauthorized response and will not trigger any pipeline actions.
Ensure the secret token in your GitLab webhook settings matches the one stored in SRE.ai. A mismatch will cause all webhook events to be rejected.
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 the 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 issuesread:jira-user— Allows SRE.ai to read user informationoffline_access— Allows SRE.ai to maintain access via refresh tokens
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 to and click Accept
You'll be returned to SRE.ai with Jira connected
Webhook URL
SRE.ai uses a Webhook URL to configure 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 uses an API Key to configure 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
API Key
Read Supabase's documentation to learn about API keys
Default Schema (Optional)
Last updated

