n8n Nodes Installation

Install the AnySite community node package for n8n

Install the n8n-nodes-anysite community node package and connect it with your AnySite API key.

Install the package

Open Community Nodes

In your n8n instance, go to **Settings → Community Nodes → Install**.

Enter the package name

Enter `n8n-nodes-anysite` and confirm. n8n installs the npm package and lists it on
[npm](https://www.npmjs.com/package/n8n-nodes-anysite).

Restart n8n

Restart the instance so the new nodes and the AnySite Agent tools are loaded.

For a self-hosted instance you can install the package directly instead:

npm install n8n-nodes-anysite

Add credentials

Create an AnySite API credential

In n8n, go to **Credentials → Create New** and search for **AnySite API**.

Paste your API key

```
YOUR_API_KEY
```

> ACTION FOR THE HUMAN: copy your API key at https://app.anysite.io/billing — an agent cannot obtain it.

The node sends it as the `access-token` header on every request.

Add an Account ID (optional)

Only required for the AnySite LinkedIn Management node (chat, connections, posts on an
authenticated LinkedIn account).

Available nodes

The package ships seven nodes:

LinkedIn

Search users and companies, read profiles, posts, reactions, comments, groups, jobs

LinkedIn Management

Connections, chat, and posting through an authenticated LinkedIn account

Twitter

User profiles, posts, and search

Reddit

Post search across subreddits

Instagram

Profiles, posts, reels, comments, likes, friendships

Job Boards

Glassdoor job listings

Web Parser

Scrape, map, and crawl any web page (beta)

Verify

Add any AnySite node to a workflow, pick the AnySite API credential, run one operation (for example LinkedIn → User → Search), and execute the node. A successful run returns JSON data in the output panel.

Troubleshooting

Nodes do not appear after installation

Restart n8n again — community node installation only takes effect after a full restart.

401 on every node execution

The credential's API key is wrong or was regenerated. See
[Authentication](/docs/authentication) for how keys and regeneration work.