n8n ON NPM
A tech stack lookup, inside your workflow
Install one community node and StackScan becomes a step like any other. Hand it a domain, get back the technologies running on it and the company behind it, then pass that to whatever comes next. Self-hosted or on n8n Cloud, both work.
Published with an npm provenance attestation, so you can verify it was built from our repository.
Installing takes about a minute
On n8n Cloud, open Settings → Community nodes → Install and enter the package name. Self-hosted, the same screen works, or install it into your n8n data directory.
n8n-nodes-stackscan
Then create a credential with an API token from My Account → API Tokens in your dashboard. n8n checks the token the moment you save it, so a bad paste fails there rather than halfway through a run.
Every step also carries a Workspace dropdown. Each workspace has its own credits and its own data, so this decides which balance a run spends.
Five operations
Three resources, covering the questions people actually ask of this data.
| Resource | Operation | Returns |
|---|---|---|
| Company | Look Up Company | The company behind a website, with industry and location. A full URL is accepted, not just a bare domain. |
| Domain | Look Up Technologies | Every technology detected on one website, each with its name, site and category. |
| Domain | Look Up Technologies in Bulk | The same for up to 100 websites in a single call. |
| Technology | Get Usage | How many websites run a technology, and where they are. |
| Technology | Start List Export | Begins a full export of every website running a technology. |
Use the bulk operation rather than looping the single lookup. It is one request instead of a hundred, and you are charged only for the domains that resolve.
What people build
The node is one step. The value is in what you attach either side of it.
Qualify a signup while they are still interested
Enrich a new CRM record
Refresh a list overnight
What it costs
Credits are charged by the API on exactly the same terms as calling it yourself. The node adds nothing on top, and n8n charges nothing for running a community node.
Bulk lookups are charged per resolved domain, so a batch of 100 where 90 resolve costs 90. A list export is one flat credit however large it is. A lookup that finds nothing is not charged at all, and the node passes the empty result through so a workflow can branch on it.
Worth knowing: a workflow on a short schedule spends real credits on every run. If you are polling the same domains, cache the answer on your side.
A community node, not yet verified
It is published to npm and installable today. Verification by n8n is a separate review, and until that clears a self-hosted instance needs community packages enabled, which is the default.
It reads only. There is no write side, because we hold no contact data of our own to push anywhere. To land StackScan data in a CRM, read it here and write it with the node that already talks to that CRM.