Supported Platforms
Jira
Atlassian OAuth integration for creating and tracking issues.
ServiceNow
OAuth 2.0 Client Credentials for incidents and change requests.
Azure DevOps
Entra ID App Registration for work item creation.
Setup Instructions
Jira
Jira
Jira connects via Atlassian OAuth. No API tokens or manual credential management required.
Authorize with Atlassian
You will be redirected to Atlassian to authorize Draftt. The app requests the following scopes:
read:jira-work— Read access to Jira projects, issues, and workflowswrite:jira-work— Create and update issues on your behalfread:jira-user— Read user information for assignment
ServiceNow
ServiceNow
ServiceNow connects via OAuth 2.0 Client Credentials — a secure machine-to-machine flow with no user interaction required at runtime.
Find your instance URL
Your instance URL is the base URL you use when logging into ServiceNow. Copy it from your browser’s address bar. It looks like:Enter this in the Draftt setup dialog.
Create a dedicated service account
Create a dedicated user for Draftt so the integration is not tied to a personal account.
- In ServiceNow, navigate to User Administration > Users
- Click New
- In the User ID field, enter a name (e.g.
draftt-service-account) - Set the Identity type to Machine
- Check the “Internal Integration User” checkbox
- Click Submit
- Open the user you just created, scroll to the Roles tab at the bottom
- Click Edit and add the following roles:
snc_read_onlycmdb_readsnc_platform_rest_api_access
- Click Save
Enable the Client Credentials grant type
Make sure the OAuth Client Credentials grant type is enabled on your instance. If the property does not exist, you will need to create it.
- Navigate to System Properties by opening:
- Search for the property
glide.oauth.inbound.client.credential.grant_type.enabled - If it exists, make sure the value is set to
true - If it does not exist, create a new property with:
- Name:
glide.oauth.inbound.client.credential.grant_type.enabled - Type:
true | false - Value:
true
- Name:
Create an OAuth inbound integration
- In ServiceNow, navigate to Machine Identity Console
- Open the Inbound Integrations tab
- Click New
- When prompted to select a connection type, choose OAuth - Client credentials grant
- Fill in a name (e.g.
draftt-oauth-app) - Under the user field, select the service account you created in Step 2 (e.g.
draftt-service-account) - In the Auth Scope section, click Create auth scope
- In the “Auth scope name” field, enter a name (e.g.
draftt-read-scope) - Under “Limit authorization to the following APIs”, add Table API
- Enable the “Allow access only to APIs in selected scope” toggle — this restricts the integration to only the APIs listed above
- Click Submit, then reopen the record and copy the Client ID and Client Secret
Azure DevOps
Azure DevOps
Azure DevOps connects via an Entra ID (Azure AD) App Registration, the same mechanism used for Azure DevOps source control.
Register an App in Entra ID
In the Azure portal, go to Entra ID > App registrations > New registration. Create a new app (e.g.
Draftt-DevOps) and copy the Client ID and Tenant ID.Generate a client secret
In the App Registration, go to Certificates & secrets > New client secret. Copy the secret value.
Add a user in Azure DevOps
In Azure DevOps, go to Organization Settings > Users > Add users. Add the App Registration’s service principal with Basic access level and Project Contributors group membership.
How It Works
When Draftt identifies a governance finding that requires action, it can automatically create a ticket in your connected platform. Each ticket includes:- The governance finding and its business impact
- Affected resources and their owners
- Recommended remediation steps
- A link back to the finding in Draftt for full context
Verifying Your Connection
After setup, return to Integrations > Ticketing in Draftt. Each connected platform shows a status:- Healthy - Draftt can create and read issues as expected.
- Unhealthy - Check that the OAuth authorization has not been revoked and that the connected user has the required permissions.