How to Connect Apify to n8n

Apify runs the scrapers behind several library systems. n8n calls it through one credential that holds your API token. This guide creates that token, stores it in n8n, and confirms the connection with a single request.

What you need

• An Apify account. The free plan includes about $5 of monthly usage credit as of 2026. Treat that figure as an estimate and check the pricing page before you rely on it.
• An n8n instance. Self-hosted and n8n Cloud both work. The steps below are identical on each.
• About 10 minutes.

Get the API token

1. Sign in to Apify Console.
2. Open Settings from the left sidebar.
3. Click API & Integrations.
4. Under Personal API tokens, click Create.
5. Give the token a name that says where it is used, for example “n8n lead gen”.
6. Copy the token right away. Apify shows the full value once. If you lose it, delete the token and create a new one.

Keep the token out of workflow JSON, chat messages, and screenshots. It grants full access to your Apify account.

Create the credential in n8n

1. In n8n, open Credentials from the left sidebar.
2. Click Add credential.
3. Search for “Apify” and select the Apify API credential.
4. Paste the token into the API token field.
5. Name the credential “Apify LGL”. Every library workflow references that name, so imports connect without edits.
6. Click Save.

n8n encrypts the token at rest. Team members with access to the credential can use it in workflows without seeing the value.

Test it

1. Create a blank workflow and add an HTTP Request node.
2. Set the method to GET and the URL to https://api.apify.com/v2/acts.
3. Under Authentication, choose Predefined Credential Type, pick Apify API, and select “Apify LGL”.
4. Click Execute step.

A 200 response with a data object containing an items array confirms the credential works. The array lists the actors in your account and may be empty on a new account. A 401 response means the token was pasted with a missing character or has been deleted in Apify Console. Create a fresh token and update the credential.

Screenshots are added once real captures replace them.

Where the library uses Apify

Sourcing workflows use Apify for two jobs: scraping building permit portals and pulling business listings from Google Maps. Both run as scheduled actors that n8n triggers and then reads back through the same credential.

Each system’s stack table lists the monthly Apify estimate for that workload. The Commercial Cleaning system budgets $30 per month at its default volume. Higher prospect counts raise that figure roughly in proportion to the number of pages scraped.