> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# TestDino Integrations

> Connect TestDino to CI, issue tracking, and messaging tools, and review which integrations are scoped per project or per organization.

TestDino integrations connect your CI/CD, issue tracking, and communication tools to test run data. Each one posts results, creates tickets, or answers questions in the tool your team already works in.

## Available Integrations

<div className="integration-cards">
  <CardGroup cols={3}>
    <Card img="https://mintcdn.com/testdino/Ua7R4RmzUY5yacWr/images/github-svgrepo-com.svg?fit=max&auto=format&n=Ua7R4RmzUY5yacWr&q=85&s=0055a83b6d8abc90fa29d665b6d88e39" title="GitHub App" href="/integrations/ci-cd/github" width="800" height="800" data-path="images/github-svgrepo-com.svg">
      PR comments, CI checks, PR dashboard sync
    </Card>

    <Card img="https://mintcdn.com/testdino/_W5tZrChGQAb05lF/images/gitlab-logo-500-rgb.svg?fit=max&auto=format&n=_W5tZrChGQAb05lF&q=85&s=0fdfd890fe016b0d6cff99fad0a21684" title="GitLab" href="/integrations/playwright-gitlab-ci" width="256" height="256" data-path="images/gitlab-logo-500-rgb.svg">
      MR comments, merge request dashboard sync
    </Card>

    <Card img="https://mintcdn.com/testdino/JwytUEY7x2_fx041/images/azure-devops.svg?fit=max&auto=format&n=JwytUEY7x2_fx041&q=85&s=f8982ec615ae9abd45220ccf3d31d1fd" title="Azure DevOps" href="/integrations/playwright-azure-devops" width="32" height="32" data-path="images/azure-devops.svg">
      View test runs inside Azure DevOps
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/jira-icon.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=bff423894156815b69e8be6acd76bbfa" title="Jira" href="/integrations/jira-playwright-test-failures" width="256" height="256" data-path="images/jira-icon.svg">
      Create issues from failed or flaky tests
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/jira-icon.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=bff423894156815b69e8be6acd76bbfa" title="Jira Forge App" href="/integrations/issue-tracking/jira-forge-app" width="256" height="256" data-path="images/jira-icon.svg">
      View linked test cases, runs, and sessions inside Jira issues
    </Card>

    <Card img="https://mintcdn.com/testdino/JwytUEY7x2_fx041/images/linear.svg?fit=max&auto=format&n=JwytUEY7x2_fx041&q=85&s=e5335dd4aa813771d3d1e2d386ecf367" title="Linear" href="/integrations/issue-tracking/linear" width="24" height="24" data-path="images/linear.svg">
      Create issues from failed or flaky tests
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/asana.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=8dfd7c08757820cbbb6ee0b5188688df" title="Asana" href="/integrations/issue-tracking/asana" width="256" height="237" data-path="images/asana.svg">
      Create tasks from failed or flaky tests
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/mon.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=3d79de1970f1f38be2d832e4749f67f4" title="monday" href="/integrations/issue-tracking/mon" width="256" height="156" data-path="images/mon.svg">
      Create items from failed or flaky tests
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/slack.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=56713fe001e7aa927c0277aa8939b3f2" title="Slack App" href="/integrations/slack-playwright-test-alerts" width="256" height="256" data-path="images/slack.svg">
      Run summaries + annotation-based failure alerts
    </Card>

    <Card img="https://mintcdn.com/testdino/FU8Ah7hBq2DoqlMO/images/slack.svg?fit=max&auto=format&n=FU8Ah7hBq2DoqlMO&q=85&s=56713fe001e7aa927c0277aa8939b3f2" title="Slack Webhook" href="/integrations/slack/webhook" width="256" height="256" data-path="images/slack.svg">
      Custom webhook notifications
    </Card>

    <Card img="https://mintcdn.com/testdino/dZnyMleO7tsw2nKM/images/openclaw-color.svg?fit=max&auto=format&n=dZnyMleO7tsw2nKM&q=85&s=f49e3a04d302b2bcf91fda5bfc5fba37" title="OpenClaw Chat Bot" href="/integrations/communication/openclaw" width="120" height="120" data-path="images/openclaw-color.svg">
      Query TestDino from Slack, Telegram, Discord, WhatsApp
    </Card>

    <Card img="https://mintcdn.com/testdino/V8kgWEComGjzGapQ/images/n8n.svg?fit=max&auto=format&n=V8kgWEComGjzGapQ&q=85&s=1e2a9dcabf0362ae6b977f58f4547fdd" title="n8n" href="/integrations/automation/n8n" width="16" height="16" data-path="images/n8n.svg">
      Trigger workflows on test runs, query data with the community node
    </Card>
  </CardGroup>
</div>

## Connection Scope

| Scope | How It Works | Integrations |
| :- | :- | :- |
| **Project-level** | Connected once per project. All team members share the same connection. | GitHub App, GitLab, monday, Azure DevOps, Slack App, Slack Webhook |
| **User-level** | Each team member authenticates individually. Tickets are created under their own account. | Jira, Linear, Asana |
| **Token-based** | Connected with a Personal Access Token. The token resolves to its project, so no project ID is entered. | n8n |

## CI/CD Integration

These are app-level connections that sync data between TestDino and your Git provider. Once connected, they post test summaries, run CI checks, and sync pull request or merge request data into TestDino automatically.

| Integration | Comments | CI Checks | PR/MR Dashboard Sync |
| :- | :- | :- | :- |
| [GitHub App](/integrations/ci-cd/github) | PR comments | Pass/fail quality gates | Full sync: overview, timeline, files changed |
| [GitLab](/integrations/playwright-gitlab-ci) | MR comments | Not available | Full sync: overview, timeline, files changed |
| [Azure DevOps](/integrations/playwright-azure-devops) | Not available | Not available | View test runs via VS Marketplace extension |

<Tip>
  Looking to upload test results from your CI pipeline? That's covered in [CI Setup](/guides/playwright-github-actions) under Getting Started. Integrations here are for app connections that sync data and post feedback.
</Tip>

## Issue Tracking

Create bug tickets directly from failed or flaky tests in TestDino. Each ticket includes prefilled context: test name, file, error message, failure history, console logs, and links to the TestDino run and Git commit.

| Integration | Supported Actions |
| :- | :- |
| [Jira](/integrations/jira-playwright-test-failures) | Create issues in a selected Jira project with prefilled fields |
| [Jira Forge App](/integrations/issue-tracking/jira-forge-app) | View test cases, runs, sessions, and releases linked from TestDino inside the Jira issue panel |
| [Linear](/integrations/issue-tracking/linear) | Create issues in a selected Linear team |
| [Asana](/integrations/issue-tracking/asana) | Create tasks in a selected Asana project |
| [monday](/integrations/issue-tracking/mon) | Create items in a selected monday board + dashboard widget to view test runs with status |

## Communication

Route test run notifications to your team's chat, and ask TestDino questions in plain language without opening the dashboard.

| Integration | What It Does |
| :- | :- |
| [Slack App](/integrations/slack-playwright-test-alerts) | • A list of notifications per project, each with its own Slack channels and users <br /> • Types: run summary, test failures, flaky tests, tag-based, annotation-based, or one you build yourself <br /> • Each notification sets its own run outcomes, test selection, and branch or environment limits |
| [Slack Webhook](/integrations/slack/webhook) | • Sends all notifications to a single channel via incoming webhook URL <br /> • One destination, no per-notification settings, tag matching, or annotation routing |
| [OpenClaw Chat Bot](/integrations/communication/openclaw) | • Two-way bot powered by the [Local MCP Server](/mcp/local) <br /> • Ask TestDino questions in plain language from Slack, Telegram, Discord, WhatsApp, and other channels OpenClaw supports |

<Tip>
  A project can hold many Slack notifications at once, so a run summary in a team channel and a failures-only alert to an on-call user are 2 separate notifications. Use an annotation-based notification to reach the owner named in your test code. See [Annotations Guide](/guides/playwright-test-annotations).
</Tip>

## Automation

Connect no-code workflows to test runs through n8n. Trigger automations when a run starts or finishes, then read test runs, test cases, specs, analytics, and usage downstream.

| Integration | What It Does |
| :- | :- |
| [n8n](/integrations/automation/n8n) | • **Trigger node**: starts a workflow when a test run begins or completes <br /> • **Action nodes**: query test runs, test cases, specs, analytics, and usage, and generate PDF reports <br /> • Runs as AI-agent tools inside n8n's AI Agent node |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.