n8n-nodes-cross-seed

Community node for n8n to drive cross-seed through its HTTP API — check the daemon and trigger cross-seed searches by info hash, name or data path.

✅ Verified community node — available directly from the node panel on n8n (self-hosted and n8n Cloud).

Installation

This is a verified community node: in n8n, click + (Add node), search for Cross-Seed, and add it — no manual install needed.

Settings → Community Nodes → Install → n8n-nodes-cross-seed. Manual / Docker deployment is also documented further down.

Then create a Cross-Seed API credential with your instance URL and API key (see below).

What it does

A single Cross-Seed node exposing:

| Operation | Description | cross-seed endpoint | |---|---|---| | Ping | Check that the daemon is running | GET /api/ping | | Trigger Search | Start a cross-seed search by Info Hash, Name or Path (with optional flags such as include single episodes) | POST /api/webhook |

Prerequisites

• A running cross-seed instance in daemon mode (cross-seed daemon) with the HTTP API reachable from n8n.
• The API key set in cross-seed's config (apiKey), if you enabled one.

Credentials

In n8n, create a Cross-Seed API credential:

• Base URL — e.g. http://cross-seed:2468 (no trailing slash)
• API Key — your cross-seed apiKey (sent as the apikey query parameter)

The credential test calls GET /api/ping.

Typical flow: cross-seed a freshly completed download

Trigger the node whenever your torrent client finishes a download, passing the torrent's info hash — cross-seed then looks for the same content on your other trackers.

flowchart LR
    A["Download client<br/>(webhook / poll)"] -->|infoHash| B["Cross-Seed<br/>Trigger Search"]
    B --> C["cross-seed finds<br/>matches on other trackers"]

You can also search by Name or Path when you don't have the info hash.

Build

npm install --ignore-scripts
npm run build                  # tsc + copy icons into dist/

Deploy to a self-hosted (Docker) n8n

n8n auto-loads packages placed in ~/.n8n/custom/node_modules/. If your n8n data dir is bind-mounted from the host into the container, copy the built package into it:

# from the project dir, after `npm run build`
mkdir -p /path/to/n8n-data/custom/node_modules
cp -r . /path/to/n8n-data/custom/node_modules/n8n-nodes-cross-seed
# then restart n8n so it re-scans custom nodes
docker restart n8n

Only package.json + dist/ are needed at runtime (n8n-workflow is a peer dependency provided by n8n itself).

Notes

• Trigger Search returns quickly; cross-seed performs the actual search asynchronously in the background — watch cross-seed's own logs for match results.
• Info Hash searches are the most reliable; Name / Path depend on your cross-seed data-dirs configuration.

Disclaimer

This is an unofficial community node and is not affiliated with or endorsed by the cross-seed project. "cross-seed" is the property of its respective authors.

License

MIT