Integrations

Connect an external issue tracker to DataKnits to raise and track issues — from data quality failures, pipeline incidents, or review workflows — without leaving the platform. All integrations are configured under Settings → Integrations. DataKnits currently supports Jira, GitHub, Azure DevOps, and ServiceNow.

Jira

Raise Jira issues directly from DataKnits. Each created issue links back to its Jira ID. Requires Jira Cloud — Jira Server / Data Center is not supported.

Prerequisites

• A Jira Cloud account at yourcompany.atlassian.net.
• A Jira project already created — you will need the project key.
• Admin or project-level permissions in Jira.
• A Jira API token (generated below).

Step 1 — Generate a Jira API Token

1. Log in to Jira using the account you want DataKnits to use.
2. Go to Atlassian account security settings: https://id.atlassian.net/manage-profile/security/api-tokens.
3. Click Create API token, give it a label (e.g., DataKnits Integration), and click Create.
4. Copy the token — you will not be able to see it again.

Step 2 — Find Your Project Key

Your project key is a short uppercase identifier (e.g., KAN, SEC, OPS).

1. Open your Jira project → Project Settings → Details.
2. The Key field shows your project key.

Alternatively, it appears in issue IDs — if issues are numbered KAN-1, KAN-2, your project key is KAN.

Step 3 — Configure in DataKnits

1. Navigate to Settings → Integrations.
2. Under Issue Tracker, select Jira.
3. Fill in the fields below, then click Test Connection.
4. Click Save once the test passes.

Step 4 — Raise an Issue

1. Click the Raise an Issue tab at the top of the Settings page.
2. Fill in the issue details and submit — the Jira issue ID is shown in the confirmation.

Troubleshooting

"No project found with key XYZ"

• Verify the project key under Project Settings → Details.
• Confirm the user email and API token belong to the same Atlassian account.
• Ensure the account has Browse Projects and Create Issues permissions.

"404 — Jira test failed"

• Verify the instance URL has no trailing slash or extra path segments.
• Confirm you are on Jira Cloud, not Jira Server/Data Center.

Authentication errors (401 / 403)

• Regenerate the API token — tokens can expire or be revoked.
• Confirm you are using Basic authentication with email + API token, not a password.

Permissions Required

• Browse Projects
• Create Issues
• Edit Issues (optional, for future update support)

GitHub

Raise GitHub issues directly from DataKnits against a specific repository. Each created issue links back to its GitHub issue number.

Prerequisites

• A GitHub account with at least read access to the target repository.
• The repository owner (user or organization) and repository name.
• A GitHub Personal Access Token (PAT) with Issues write permission.

Step 1 — Generate a GitHub Personal Access Token

1. Log in to GitHub using the account you want DataKnits to use.
2. Go to Settings → Developer settings → Personal access tokens.
3. Click Generate new token. Fine-grained tokens are recommended.
4. Set an expiration. For fine-grained tokens, select the target repository under Repository access.
5. Under permissions, grant Issues: Read and write.
6. Click Generate token and copy it — you will not be able to see it again.

Step 2 — Find Your Repository Owner and Name

Both values come directly from the repository URL: https://github.com/<owner>/<repo>.

• Repository owner — the user or organization (e.g., acme-corp).
• Repository name — the part after the owner (e.g., data-pipeline).

Step 3 — Configure in DataKnits

1. Navigate to Settings → Integrations.
2. Under Issue Tracker, select GitHub.
3. Fill in the fields below, then click Test Connection.
4. Click Save once the test passes.

Step 4 — Raise an Issue

1. Click the Raise an Issue tab at the top of the Settings page.
2. Fill in the issue details and submit — the GitHub issue number is shown in the confirmation.

Troubleshooting

"404 — Repository not found"

• Confirm owner/repo spelling — GitHub repository names are case-sensitive.
• For private repositories, confirm the token includes the repo scope (classic) or the repository is in the fine-grained token's access list.

"401 — Bad credentials"

• The token may have expired or been revoked — regenerate it.
• Confirm there is no extra whitespace around the token when pasting.

"403 — Resource not accessible by personal access token"

• The token is missing the Issues: Read and write permission — regenerate with the correct scope.

Permissions Required

• Read access to the repository
• Issues: Read and write — granted on the Personal Access Token

Azure DevOps

Raise Azure DevOps work items directly from DataKnits against a specific project. Each created item links back to its ADO work item ID.

Prerequisites

• An Azure DevOps organization at https://dev.azure.com/yourorganization.
• A project already created within that organization.
• A Personal Access Token (PAT) with Work Items — Read & write scope.

Step 1 — Generate an Azure DevOps Personal Access Token

1. Log in to Azure DevOps using the account you want DataKnits to use.
2. Click your profile icon (top right) → User settings → Personal access tokens.
3. Click + New Token. Set a name, expiration, and organization.
4. Under Scopes, select Work Items → Read & write.
5. Click Create and copy the token — you will not be able to see it again.

Step 2 — Find Your Organization and Project Name

• Organization name — from your ADO URL: https://dev.azure.com/yourorganization.
• Project name — visible under Project Settings → Overview, or in the URL: dev.azure.com/yourorganization/YourProject.

Step 3 — Configure in DataKnits

1. Navigate to Settings → Integrations.
2. Under Issue Tracker, select Azure DevOps.
3. Fill in the fields below, then click Test Connection.
4. Click Save once the test passes.

Step 4 — Raise an Issue

1. Click the Raise an Issue tab at the top of the Settings page.
2. Fill in the work item details and submit — the ADO work item ID is shown in the confirmation.

Troubleshooting

"TF200016 — Project does not exist"

• Confirm the project name spelling — it is case-sensitive.
• Confirm the PAT account is a member of the project.

"401 / VS800075 — Access Denied"

• Regenerate the PAT and confirm the scope includes Work Items → Read & write.
• Confirm the organization URL has no trailing slash.

"TF400813 — User not authorized"

• Confirm the account has at least Basic access level — Stakeholder access cannot create work items in private projects.

Permissions Required

• View work items in this project
• Edit work items in this project
• Basic access level or higher on the ADO organization

ServiceNow

Raise ServiceNow records (e.g., Incidents) directly from DataKnits against a target table. Each created record links back to its ServiceNow record number.

Prerequisites

• A ServiceNow instance URL (e.g., https://yourcompany.service-now.com).
• A ServiceNow account with permission to create records on the target table.
• Confirmation from your ServiceNow administrator of which authentication mode is enabled — Basic Auth or OAuth 2.0.

Step 1 — Prepare ServiceNow Credentials

ServiceNow supports two authentication modes, configured at the instance level by your administrator:

• Basic Auth — use the username and password of the integration account. A dedicated service account is recommended.
• OAuth 2.0 — ask your ServiceNow administrator to register an application in System OAuth → Application Registry and provide you the Client ID and Client Secret.

Step 2 — Find Your Instance URL and Table Name

• Instance URL — the base URL of your ServiceNow instance, e.g., https://yourcompany.service-now.com.
• Table name — the table records should be created in, e.g., incident, problem, or a custom table. Visible under System Definition → Tables. The table name also appears in the list view URL — .../incident_list.do maps to table name incident.

Step 3 — Configure in DataKnits

1. Navigate to Settings → Integrations.
2. Under Issue Tracker, select ServiceNow.
3. Fill in the fields below, matching the authentication mode confirmed in Step 1.
4. Click Test Connection to verify the setup.
5. Click Save once the test passes.

Step 4 — Raise an Issue

1. Click the Raise an Issue tab at the top of the Settings page.
2. Fill in the record details and submit — the ServiceNow record number is shown in the confirmation.

Troubleshooting

"401 — User Not Authenticated"

• Confirm the username/password or Client ID/Secret are correct and not expired.
• Confirm the account is active and not locked out in ServiceNow.

"403 — Insufficient rights"

• Confirm the integration account has the appropriate role for the target table (e.g., itil for the Incident table).
• Confirm Access Control (ACL) rules permit record creation for this account.

"Instance URL not reachable"

• Confirm the URL is exactly https://yourcompany.service-now.com with no trailing slash.
• Confirm your network/firewall allows outbound connections to the ServiceNow instance — relevant for on-prem DataKnits deployments.

Permissions Required

• A role with create access on the target table (e.g., itil for Incident)
• REST API access not blocked by instance-level ACLs