Skip to main content
What you’ll learn
  • What the TestDino n8n node does
  • How to install the node and connect your project
  • How to trigger workflows on test runs
The @testdino/n8n-nodes-testdino community node connects TestDino to n8n. Trigger workflows when a test run starts or finishes, query test runs, test cases, specs, analytics, and usage, and generate PDF reports. The nodes also run as AI-agent tools inside n8n’s AI Agent node.
n8n is a third party platform maintained by n8n.io. This guide covers only the TestDino node and setup.

​
Quick Reference

SectionWhat it covers
PrerequisitesTestDino project, running n8n, a PAT
Install the nodeAdd the community node from the n8n UI
Connect your projectCreate the TestDino API credential
Trigger on test runsFire workflows when runs start or finish
Query TestDino dataRead runs, cases, analytics, and reports
TroubleshootingCommon failures and fixes

​
Prerequisites

  • TestDino project. Sign up at app.testdino.com.
  • n8n running with community nodes enabled, on Node.js 18 or later.
  • Personal Access Token with the public-api scope (format tdp_...).

​
Install the node

Find the node on n8n’s integrations directory. In n8n, go to Settings → Community Nodes → Install, enter the package name, and confirm: 
@testdino/n8n-nodes-testdino
Self-hosted installs can add it from the command line, then restart n8n: 
npm install @testdino/n8n-nodes-testdino
This adds two nodes: TestDino (query and actions) and TestDino Trigger (webhook events).

​
Connect your project

The credential holds one field, your Personal Access Token. The project is discovered from the token, so you never enter a project ID.
1

Create a Personal Access Token

In TestDino, open Project Settings → API, create a token with the public-api scope, and copy the tdp_... value. It is shown once.
2

Add the TestDino API credential

In n8n, go to Credentials → New → TestDino API, paste the token, then click Save and Test. The test resolves the bound project and confirms the scope.
One token connects one project. Store it in a password manager, never commit it to Git, and revoke tokens you no longer use.

​
Trigger on test runs

The TestDino Trigger node starts a workflow on run events. It self-registers a webhook with TestDino when the workflow is activated.
EventFires when
Run StartedA new test run is created
Run FinishedA test run completes
For Run Finished, set Trigger On to scope the event:
Trigger OnBehavior
Any OutcomeEvery finished run
Failures OnlyOnly runs with failures
Passing OnlyOnly runs with no failures
The filter is applied server-side, so failure-only alerts need no extra IF node. The n8n instance must expose a publicly reachable production webhook URL for events to arrive.

​
Query TestDino data

The TestDino node reads project data and generates reports. Pick a resource and operation:
ResourceOperations
Test RunGet, Get Many
Test CaseGet, Explore, Get History
SpecGet Many
Manual TestGet, Get Many, Get Suites
DashboardGet
AnalyticsGet Summary
UsageGet
ReportGenerate PDF
List operations support Return All to walk every page, or a Limit for a single page. Generate PDF returns a binary file you can attach in a later node. Both nodes set usableAsTool: true, so n8n’s AI Agent node can call them as tools. An agent can fetch failed runs, summarize release health, or generate a report on request.

​
Example workflows

TestDino Trigger (Run Finished, Failures only) → TestDino (Test Run, Get) → Slack
Schedule (Monday) → TestDino (Report, Generate PDF) → Gmail
Schedule (Daily) → TestDino (Usage, Get) → IF usage > 80% → Slack warning

​
Troubleshooting

Confirm the token starts with tdp_, was copied in full, has the public-api scope, and is not revoked.
The workflow must be active and the n8n production webhook URL must be publicly reachable. Check that no firewall blocks TestDino, the token is valid, and the outcome filter is not excluding the run.
Confirm the package is installed, community nodes are enabled, n8n was restarted, and the package name is exact (@testdino/n8n-nodes-testdino).
Large projects hold many runs and cases. Disable Return All and use filters or a Limit instead.
https://mintcdn.com/testdino/dZnyMleO7tsw2nKM/images/openclaw.svg?fit=max&auto=format&n=dZnyMleO7tsw2nKM&q=85&s=50633fb37ad8a16b8ee15dbb8af4369d

OpenClaw Integration

Ask TestDino about Playwright failures from your team chat

TestDino MCP overview

What the MCP server does and which tools it exposes

API Reference

Endpoints the n8n node calls under the hood