The blank canvas is the pitfall, not the starting line

The mistake beginners make most often in week one is opening a blank canvas and then sitting in front of it, thinking “…which node do I drag in?” Half an hour goes by and nothing has moved.

Meanwhile there is roughly an 80% chance that somebody has already built the thing you want to build — and built it better than your first attempt would be.

Copying somebody else's template is not laziness. It is the fastest way to see how n8n puts nodes together. You will have a working workflow in front of you inside thirty minutes, which beats two weeks of feeling your way alone.

So the goal for this part is narrow and achievable: get somebody else's workflow running inside an hour. Building your own from scratch by hand waits until Part 6 of this series. By then you will have five or six finished workflows behind you, and it will feel like a completely different exercise.

Where the templates actually live

First, a misreading worth clearing up, because it shapes everything else. n8n itself has no built-in, offline template gallery. The two entry points you think you are seeing lead to the same place: the public n8n.io/workflows/.

flowchart LR
  A["Templates in the left sidebar
of Woow n8n"] --> C["n8n.io/workflows/
the one public pool"]
  B["The address typed
straight into your browser"] --> C
  C --> D["A template detail page:
preview, description,
nodes used, author, Last update"]
  D --> E["Use for free
then Copy template to clipboard"]
  E --> F["Your own canvas in Woow n8n,
pasted on an empty spot"]

One honesty note about the source material this series is built from. The chapter on the Templates gallery is explicit that both routes reach the same public pool. The next chapter, on importing JSON, describes the sidebar route as the “built-in version” and n8n.io/workflows as the “community version,” as though they were two different collections. The two chapters disagree, and the correction is the one that carries the detail, so this article follows it: one pool, two doors. If your own sidebar shows an in-app gallery that never leaves the tab, see the next callout — that is a real configuration, and it means your company has one.

Ten seconds that rule out most of the duds

The pool is large and not every template suits you. Five things to look at will rule out around 80% of the ones that would have wasted your afternoon, and you can run the whole list in about ten seconds on the detail page.

Those five run in the same order every time, and each one can end the decision on its own.

flowchart TD
  A["A template that looks
about right"] --> B{"More than 15 nodes?"}
  B -->|"yes"| X["Skip it for now.
Come back when you
can read a big one"]
  B -->|"no"| C{"Official account or
Verified Creator?"}
  C -->|"no, and no name either"| X
  C -->|"yes"| D{"Last update within
the past year?"}
  D -->|"no, two years old"| X
  D -->|"yes"| E{"Do you recognize
the services it uses?"}
  E -->|"no"| X
  E -->|"yes"| F{"Does the description say
what it is for?"}
  F -->|"no"| X
  F -->|"yes"| G["Worth copying.
Press Use for free"]

From the gallery to your own workflow

There is really one route, with two ways of starting it. Either click Templates in the left sidebar of Woow n8n, which opens another browser tab at n8n.io/workflows/, or type that address into the browser yourself. Experienced users type it; it saves a click. Everything after step 1 is identical.

1. Step 1

   Open the gallery

   Signed in to Woow n8n, the left sidebar carries a Templates item alongside Workflows, Executions and Credentials. Clicking it opens another browser tab pointed at n8n.io/workflows/. Or skip that and open the address directly:

   https://n8n.io/workflows/

   If you cannot see Templates in the sidebar at all, go back to Part 2 of this series and get familiar with the workspace first. The home page of the gallery is packed and it startles most people the first time. That is normal.

2. Step 2

   Filter by category, service or keyword

   Categories run down the left — AI, Sales, IT Ops, Marketing, Document Ops, Support. You can also narrow by service icon (Google Sheets, OpenAI, Telegram, Gmail) or type a keyword into the search bar at the top. Keywords that work well when you are starting out:

   slack notification — the shortest useful thing to automate first

   rss to notion — a scheduled fetch with a write at the end

   ai email summary — adds a model to the chain without much else

   For something AI-flavored built on a specific service, type the service name — Airtable, Notion, Line, Typeform — and then tick AI in the filters on the left.

3. Step 3

   Open it and run the five checks

   The detail page gives you three things: a Preview of the node diagram, so you can see at a glance how complicated the logic is; a Description saying what the author built it for; and the list of nodes used and credentials needed. Thirty seconds here beats copying it over and taking it apart afterwards by a factor of ten.

   If the preview looks like a pile of nodes you do not recognize, go back and pick another one. That is the check working, not you being fussy.

4. Step 4

   Use for free, then Copy template to clipboard

   The Use for free button sits in the top-right corner of the detail page. Clicking it opens a small dialog with two main options: Copy template to clipboard, which puts the whole workflow JSON on your clipboard, or a jump to n8n Cloud to try it there. Choose Copy. A small “Copied!” hint flashes, and your clipboard now holds a large blob of JSON.

   The two source chapters describe that button as orange in one place and green in another, which is a good reminder that button colors and wording drift between versions. Recognize the button by its position and its label rather than by its color.

5. Step 5

   Back to Woow n8n, on a blank workflow

   Return to your n8n.woowtech.io tab. On the Workflows page, press + Add workflow for a blank one. Pasting does not overwrite anything — the nodes land on whichever workflow you currently have open — but starting blank keeps a borrowed workflow from getting tangled up with work you already have.

6. Step 6

   Click an empty spot on the canvas, then paste

   Move the mouse to an empty spot in the middle of the canvas — not onto a node, not into the workflow name field at the top — single-click it, and press Ctrl+V. On a Mac that is Cmd+V. Every node drops in at once, connections and original relative positions included. If the shortcut does nothing, right-click the empty space for a Paste option.

7. Step 7

   Rename it and save

   The name in the top-left corner is usually a default such as My workflow, or the English name the original author gave it. Click it and change it to something you will recognize in a list of forty. A purpose-then-service shape works well:

   rss_morning_digest_slack

   Then press Save in the top-right corner, or Ctrl+S. A refresh before you save loses the lot.

When somebody hands you a file instead

You do not have to go through the gallery at all. A colleague sends you my_workflow.json on Slack, or somebody posts a workflow to a GitHub Gist. Two ways in, and they are functionally identical.

For a very large workflow — a few hundred nodes — the file route is less likely to choke on the clipboard. Otherwise use whichever suits you.

Everything except the keys

Every workflow you drag together on the canvas is a JSON file underneath. Knowing what that file holds explains both why importing works so smoothly and why the imported thing does not run yet.

The last row is the one that matters. The secret part of a credential does not travel with the JSON. Sharing a workflow will not leak your API key by accident, and a workflow somebody shares with you does not hand you their account. What normally survives is a short reference fragment, nothing more:

That id belongs to the original author's instance. Pasted into yours it resolves to nothing, which is why the node shows up red with a “credential not found” complaint. The red is not damage. It is the design working, and it is the reminder to connect your own.

flowchart LR
  subgraph S["Stays behind, in the author's instance"]
    direction LR
    S1["The actual password,
OAuth token or API key"] --> S2["Reachable only by
the original author's
credential store"]
  end
  subgraph T["Travels inside the JSON"]
    direction LR
    T1["nodes
type, position, parameters"] --> T4["Pasted onto
your canvas"]
    T2["connections
which node feeds which"] --> T4
    T3["A credential reference:
an id and a name only"] --> T4
    T4 --> T5["Node shows red:
credential not found.
Connect your own"]
  end

Sending one the other way

Built something useful and want to hand it to a teammate? Open the workflow, use the three-dot menu in the top right and choose Download. That saves a .json file to your machine, named after the workflow. Send it by Slack, email or shared drive; the person on the other end pastes or imports it exactly as described above.

Red nodes, one manual run, then Active

Importing a template borrows a skeleton. It will not run yet. Three things, in this order, produce the fewest mistakes.

1. First

   Check every node for a red marker

   A red dot or exclamation mark means the node is missing something. Eight times out of ten it is the credential; less often a required field is empty, such as the recipient email address. Start from the most upstream Trigger node and work your way down.

2. Second

   Check which outside services it wants, and whether you have them

   If the template uses Airtable and your company has no Airtable account, that template is no use to you. Give up on it early and pick another. You can swap it to Google Sheets instead, but that is editing rather than importing, and Part 4 covers it.

3. Third

   Run Execute workflow by hand

   The Execute workflow button sits in the bottom-right corner. Green checks all the way through are the only thing that proves the chain works. Until a manual run succeeds, leave the Active toggle in the top-right corner off.

Spotting which nodes need a credential

The workspace tells you three ways, and it is worth knowing all three because the first one is easy to skim past on a crowded canvas.

• A red border, or a small red exclamation icon at the top of the node. That is n8n saying outright that this node is not ready.
• The Parameters panel. Open the node and look at the credential dropdown at the very top. It reads No credentials selected, or shows an error message on a red background.
• The shape of the canvas. The red nodes usually form a chain, so one glance across the whole workflow tells you the scale of what needs fixing.

Connecting one

1. Step 1

   Click the red node to open Parameters

   Double-click the node, or single-click it and use the panel on the right. Its contents expand.

2. Step 2

   Find the credential dropdown at the very top

   If the dropdown already lists a credential of the same kind that you set up earlier — a Slack OAuth credential from a previous workflow, say — pick it. If not, choose Create New Credential at the bottom of the list.

3. Step 3

   Fill in the account, authorize, or paste the key

   Every service asks for something different. Slack uses OAuth, Airtable uses a Personal Access Token, and an HTTP Request node can be left with no credential at all. Part 10 of this series goes through every credential type; for now, follow what the form in front of you asks for.

4. Step 4

   Save, then check the red is gone

   Press Save. Back on the canvas that node should go from a red border to a normal gray one. Only once every node is gray is it worth pressing Execute workflow.

flowchart TD
  A["Nodes pasted onto
your canvas"] --> B{"Any node showing
a red marker?"}
  B -->|"yes"| C["Open it, connect a credential
or fill the empty field"]
  C --> B
  B -->|"no, all gray"| D["Execute workflow, by hand"]
  D --> E{"Green all the way
through?"}
  E -->|"no"| F["Read the failing node's error.
Fix one thing, run again"]
  F --> D
  E -->|"yes"| G["Run it once more
against real data"]
  G --> H["Now switch on Active"]
  E -->|"skipped, toggled Active anyway"| Z["Error logs pile up
overnight on a schedule"]

The six that account for most of it

Six failures cover most of what actually goes wrong between the gallery and a running workflow.

1. 1

   Clicking Templates in the sidebar does nothing

   It should open another browser tab at n8n.io/workflows/. If nothing happens, work through three causes in order. The browser blocked the popup — click the popup notice at the right of the address bar and allow it. The company network blocks n8n.io — type the address into the browser to test. Or IT has genuinely blocked it, in which case take the “import a JSON file somebody else downloaded” route from the previous section.

2. 2

   You paste the JSON and nothing arrives

   Nine times out of ten something went missing during the copy — you picked up only part of the text. Go back to the template page and press Use for free then Copy template to clipboard again; that is what copies the complete JSON. And make sure you clicked an empty spot on the canvas before pasting, not a node.

3. 3

   The JSON turned into plain text instead of nodes

   Your focus was in the wrong place. Either you clicked the workflow name box at the top, so the JSON became the workflow's name, or you clicked a sticky note or a field inside a node, so the JSON went into that field. Single-click an empty spot on the canvas to move focus back, then paste again.

4. 4

   Every pasted node is a red error

   Two main causes. Either the credentials are not set yet, which is the usual one — click each red node and connect one. Or your n8n does not have the node version the template uses, in which case Unknown node type shows at the bottom, and the only ways out are a newer template or upgrading n8n.

5. 5

   The template needs a node you cannot find

   The node may not be in the n8n community edition — some are enterprise-only — or your company may have disabled that integration on Woow n8n. Ask IT, or switch to a template built from basic nodes plus HTTP Request. That node can stand in for almost any SaaS-specific one, and Part 9 of this series is about it.

6. 6

   Only half the workflow seems to be on screen

   The rest of the nodes are sitting off to the bottom right of the canvas, outside your view. Press Fit to view on the control bar in the bottom-right corner of the canvas — the magnifier aimed at a screen — or press the 1 key to zoom out until the whole thing appears.

flowchart TD
  A["You pressed paste and
no nodes appeared"] --> B{"Did the JSON text
show up somewhere
on the page?"}
  B -->|"in the workflow name box"| C["Focus was on the title.
Undo it, click empty canvas,
paste again"]
  B -->|"inside a node field
or a sticky note"| D["Focus was inside that field.
Clear it, click empty canvas,
paste again"]
  B -->|"nowhere at all"| E{"Did you press Copy template
to clipboard on the detail page?"}
  E -->|"no, selected the text by hand"| F["Go back and use the button.
Hand selection usually
picks up only part of it"]
  E -->|"yes"| G["Click an empty spot on the
canvas to give it focus,
then paste again"]

Older workflows, and what breaks in them

n8n ships a major version every few months. Nodes get renamed and parameters get rearranged. Pull a workflow from 2021 off the gallery, paste it into a relatively recent Woow n8n, and these are the problems you are most likely to hit.

The ones that come up every time

Where to go from here