How to Set Up n8n for the Library Systems

n8n is the automation platform every system in this library runs on. The workflows you download are n8n JSON files, and each tool credential you create lives inside your n8n instance. Set it up once and every later guide takes minutes.

What you need

• A decision between n8n Cloud and self-hosting. Both run the library workflows without edits.
• For self-hosting, a small VPS. 2 GB of RAM is enough for these workloads.
• About 30 minutes for cloud, closer to an hour for a first self-hosted install.

Cloud or self-hosted

n8n Cloud is the fast path. You get a running instance in a few minutes, updates are handled for you, and the starter tier covers the execution volume these systems generate. It costs about $24 per month as of 2026.

The system pages in this library quote n8n Cloud in their cost tables, and as an n8n partner it is what we recommend. Self-hosting trades that convenience for a lower bill: a $10 VPS runs the whole stack. The official Docker image is the supported route. Expect to spend some time on the initial install, a domain, and HTTPS.

If you have never run a server, start on cloud. You can export your workflows and credentials later and move them to a VPS in an afternoon.

Create the instance

1. For cloud, sign up at the n8n site, verify your email, and pick a workspace name. The instance is live immediately.
2. For self-hosting, pull the Docker image on your VPS, set the N8N_HOST and WEBHOOK_URL environment variables to your domain, and put a reverse proxy with HTTPS in front. The n8n docs cover this with copy-paste compose files.
3. Open the editor URL and create the owner account. This account manages users and credentials, so use a password manager.

Import a library workflow

1. Download a system’s workflow JSON files from its page.
2. In the n8n editor, open Workflows and click Add workflow, then choose Import from file.
3. Pick the first file, WF1. The canvas loads with sticky notes that explain each section.
4. Repeat for the remaining files. Import them all before wiring credentials so you can see every credential the system expects.

Nodes that need a credential show a warning triangle until you create one. The setup guide for each tool in the stack walks through its credential.

Set the timezone

This is the step people skip. Schedule triggers fire in the instance timezone, and a fresh install defaults to UTC. Open Settings, find the timezone field, and set your local zone before activating anything. A sourcing workflow meant for 6 a.m. that actually runs mid-afternoon will hit rate limits alongside everyone else’s traffic and your daily batches will land late.

What it costs

Budget about $24 per month on cloud starter, or $10 per month self-hosted. Execution volume from a single library system stays far below either tier’s limits, so the bill does not grow with prospect count the way scraping and enrichment tools do.

Where the library uses n8n

Everywhere. Sourcing, enrichment, outreach, reply handling, and quoting are all n8n workflows, and every other setup guide on this site assumes your instance is running. When a system page lists its stack, n8n is the layer that connects the rest.