Skip to main content
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

​
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 td_pat_ prefix, granted access to the project you want to automate. The n8n node uses the same PAT as the MCP server.

​
Install the node

TestDino is a verified node, so you install it from the editor without leaving the canvas. The marketplace lists it as two entries, TestDino and TestDino Trigger, but both ship in one package.
1

Open the Nodes panel

In the n8n editor, click + in the top right to open the Nodes panel.
2

Find the verified node

Search for TestDino and look for the result with the verified badge. Click Install node.
3

Use it in a workflow

Drag the TestDino or TestDino Trigger node onto the canvas and connect it like any other node.
On a shared instance, an owner installs the verified node once. After that, everyone on the instance can use it. The install adds both nodes from one package.

​
Connect your project

The credential holds one field, your Personal Access Token. The PAT can reach any project you have access to.
1

Create a Personal Access Token

In TestDino, open User Settings → Personal Access Tokens, generate a token with access to the project you want to automate, and copy the td_pat_... 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 confirms the token and its scope.
Store the token 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. For On run finished, set Trigger On to scope the event: 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. Each row below is one action in the node panel, grouped by resource: List actions support Return All to walk every page, or a Limit for a single page. Generate a PDF report returns a binary file you can attach in a later node. Get available filters returns the environments, branches, developers, and tags in a project, so you can populate later nodes with valid filter values. 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 workflow:

​
Troubleshooting

Confirm the token starts with td_pat_, was copied in full, covers the project you are querying, 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.

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