Skip to main content
Free plan, no cardStart free
Integrations · 17 listed · each one names the code that implements it · checked 2026-10-21

Integrations, by the job they do

Everything the product connects to, grouped by the job it does. There is no marketplace and nothing to install in the other tool: each integration is a REST call, a generated file or an import the product performs with a credential you issue. Nothing is listed that is not in the code.

CI/CD

GitHub Actions

Dokimore has no GitHub Action, command-line tool or CI token today. What works is the exit path: copy a recording as a @playwright/test spec, commit it, and let a workflow you own run it on every push, failing the job when a test fails.

Set up GitHub Actions

GitLab CI

There is no Dokimore runner, token or pipeline template for GitLab today. A recording copied as a @playwright/test spec runs in any GitLab pipeline, and Playwright’s JUnit reporter feeds GitLab’s own test report.

Set up GitLab CI

Jenkins

Dokimore does not start Jenkins jobs or read their console output today. An exported test is plain framework code, so a declarative Jenkinsfile runs it like any other suite and the junit step records the result.

Set up Jenkins

Azure DevOps

Dokimore has no Azure DevOps connection for customers today. A recording exported as a @playwright/test spec runs in any Azure pipeline, and the PublishTestResults task shows each test in the run summary.

Set up Azure DevOps

Bitbucket Pipelines

Dokimore does not read Bitbucket pipelines or steps today. An exported test is ordinary Playwright, Selenium or Robot Framework code, so one pipeline step runs it and Bitbucket’s test reporting picks up the JUnit file.

Set up Bitbucket Pipelines

Any CI system

A CI system cannot start a Dokimore run today: there is no webhook trigger, no command-line runner to install and no CI token. Exported code is the path that works, in any system that can run Node or Python.

Set up Any CI system

Alerting and chat

Slack

An alert sink of type Slack posts a Slack attachment to your incoming-webhook URL whenever a synthetic monitor raises an alert at or above the severity you set. Test runs, failed checks and recordings do not post to Slack today.

Set up Slack

Microsoft Teams

A Teams alert sink posts a MessageCard to an incoming-webhook URL when a synthetic monitor raises an alert, with a theme colour for info, warning or critical. The card has no button that opens a run, and runs do not post to Teams.

Set up Microsoft Teams

PagerDuty

There is no PagerDuty connection for customers today: no Events API v2 payload, no routing-key field and no incident per run. Synthetic-monitor alerts can still reach on-call through an Opsgenie sink, or through a generic webhook sink pointed at a relay of your own.

Set up PagerDuty

Opsgenie

An Opsgenie alert sink posts to the Alert API URL you paste, authenticated with an Authorization: GenieKey header carrying your integration key, whenever a synthetic monitor raises an alert at or above your minimum severity.

Set up Opsgenie

Webhooks

A generic alert sink posts each synthetic-monitor alert at or above your minimum severity as a JSON body to the URL you set. There is no HMAC signature, no custom header, no event choice and no run-completion event yet.

Set up Webhooks

Issue tracking

Jira

Smart test selection imports an issue from Jira, Linear or GitHub by its URL: it fetches the issue with a token used once and never stored, and analyses the text the way it analyses an uploaded requirements document. Creating Jira issues from failed runs is not available.

Set up Jira

Imports

Postman, Bruno, Insomnia and Hoppscotch

The API studio imports Postman v2.1, Bruno, Insomnia and Hoppscotch collections into folders, requests, variables and auth, and returns a report that names every item it skipped and every auth type, script, variable or body it translated.

Set up Postman, Bruno, Insomnia and Hoppscotch

OpenAPI and cURL (HAR to read)

The studio turns an OpenAPI 2.0, 3.0, 3.1 or 3.2 document into requests that keep their contract snapshot, and a cURL command pasted into the Import dialog into a request. A HAR file can be opened and read in the browser, but its entries are not imported as requests yet.

Set up OpenAPI and cURL (HAR to read)

Exports

Playwright, Selenium, Robot Framework and pytest export

The code emitter turns a recording’s steps and locators into Playwright TypeScript or Python, Selenium for Python, Robot Framework with the Browser library, or pytest code; the export is the exit path from the platform and the way tests reach your CI.

Set up Playwright, Selenium, Robot Framework and pytest export

k6

On the load screen, Export as k6 script saves a JavaScript file that sends the same targets with the same weights, virtual users, ramp-up, duration and wait between requests; an attached data set is saved beside it as data.csv. The script is written in your browser, so nothing is sent anywhere to produce it.

Set up k6

Workflow automation

n8n and connectors

The workflow canvas imports an n8n workflow JSON and maps HTTP Request, Slack, Mattermost, Telegram, WordPress, Reddit, filter, limit and database nodes to keyword nodes, reporting each node as mapped, folded, trigger, skipped or unsupported; Code nodes are unsupported because no arbitrary JavaScript runs.

Set up n8n and connectors

How this directory is kept honest

  1. Every page names the file in our own code that does what it describes, and describes only what a signed-up customer can use today through a screen they can open.
  2. Anything that is not built yet, such as a CI trigger, a command-line runner or a PagerDuty connection, is stated as not available rather than implied.
  3. Imports and exports are listed in the direction they actually work. Where a direction does not exist (JMX, Selenium code in, HAR into requests) the page says so.
  4. The date on each page is the last time its claims were checked against the code and against what a customer account can reach.

Questions buyers ask

Is there an integrations marketplace or an app to install?

No. Every integration is an alert sink you configure, an export you copy, or an import the product performs itself; nothing is installed in the other tool.

Can my CI pipeline start a Dokimore run?

Not yet. There is no webhook trigger, command-line runner or CI token. Tests exported as Playwright, Selenium or Robot Framework code run in any CI today.

Why does each page list a file path?

Because a claimed integration that is not in the code is a false claim. The path is the evidence, a test checks that it exists, and the page says what a customer can reach.

Connect it to the pipeline you already run

Start on the Free plan: code export, collection imports and monitor alert sinks work on every plan.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India