← All tools & templates
GuideSome setup

Getting Started with n8n

What n8n is, how to run it, and how to import any of the workflow files on this site.

n8n is a tool for connecting the software you already use so that things happen on their own. You build, or import, a workflow of small steps: when this happens, do that, then that. Every automation on this site comes as an n8n file you can import. This page gets you from nothing to your first running workflow.

What's inside

  • What n8n is and the two ways to run it
  • How to import a workflow file, step by step
  • How to connect Gmail, Google Sheets and an AI model
  • The common problems and what they usually mean

Two ways to run it

Both run the same workflow files. The difference is who looks after the server.

Plans and prices change, so check n8n's own pricing page. One thing worth knowing: n8n counts one run of a whole workflow as a single execution, while Zapier counts each step separately as a task. For workflows with several steps that can make a big difference to the bill.

Import a workflow

  1. Download the .json file from the page of the automation you want.
  2. In n8n, create a new workflow, open the ⋯ menu at the top right, and choose Import from file.
  3. The workflow appears on the canvas. Sticky notes on the canvas explain the setup in the same order as the page.
  4. Click each node that shows a warning and connect your own account.
  5. Open the node called Settings and replace the sample values with your own.
  6. Click Execute workflow to run it once, then click each node to see what went in and what came out.
  7. Switch the workflow to Active when you're happy with it.

The files contain no logins or keys. Your connections stay in your own n8n and are never part of the file.

Connect your accounts

Each AI step costs a small amount every time it runs. Your AI provider's dashboard shows exactly what you're spending, so check it during the first week.

Web addresses that start a workflow

Some workflows start when another tool sends them a web request. The first node shows two addresses. The test address only works while you're clicking to listen in the editor. The production address works once the workflow is Active. Use the production address in your other tools.

When something doesn't work

Be careful with customers

  • Start every customer-facing workflow in draft or test mode and read the first batch yourself.
  • Texting customers needs their permission and a way to opt out.
  • Don't send information you wouldn't want stored by an AI service. Check your provider's privacy terms.
  • An AI can be wrong. Keep a person in the loop for anything involving money, promises or sensitive topics.
When low-code stops and custom software starts →

More tools & templates

Rather have someone choose and build it?

I'll look at how your business runs, pick the right setup, and build it. Book a 30-minute call and I'll tell you honestly what makes sense.