AI Folks
  • Courses
  • Web Of AI
  • Pricing
  • Enterprise
Log in
PreviousWhat n8n isNextData between nodes

Vibe Coder · Unit 15: Workflows With n8n · Lesson 2 of 6

Your first workflow

Build a real workflow end to end: a signup form comes in, a row is saved, a welcome message goes out. Test each node, then publish.

Read the short notes and pictures.Do everything inside a blue frame.

A workflow worth having

Tutorials often start with a toy. Start instead with something your product needs on day one: handling a new signup. It has every part of a real workflow and you will keep it.

Teal tiles, hand-drawn. Four nodes: new signup, save to a table, send welcome, notify me.
The plan: one trigger and three actions.

Build it in this order

  1. 1

    Create a workflow and add the trigger

    For now use a form trigger or the Webhook node, so you can send a test signup yourself.

  2. 2

    Run the trigger once

    Submit one test signup. Open the node and read its output. This is the data every later node will use.

  3. 3

    Add the "save" node

    Choose your table’s node: Airtable or Supabase. Create the credential when asked. Map name and email into columns.

  4. 4

    Run and check the table

    A row should appear. If not, the node shows the error.

  5. 5

    Add the welcome message

    An email node, or an HTTP Request to your email service. Use the name from the trigger in the text.

  6. 6

    Add the notification

    A message to yourself in the chat tool you use.

  7. 7

    Publish

    Until you publish, the workflow only runs when you press the button.

Reading a node’s output

Every node shows you what it received and what it produced. Get used to opening that panel after each run. Most workflow bugs are a field with a different name than you expected, and you can see that immediately in the output.

Teal tiles, hand-drawn. A code window shows the trigger output: name, email and plan.
The trigger’s output is the data the rest of the workflow uses.

Credentials

A credential is how n8n is allowed to act in another service for you: an API key or a sign-in. You create it once and any node for that service can use it. Credentials are stored separately from workflows, so sharing a workflow does not share your keys.

Give each credential the least access that works

If a node only needs to add rows to one table, do not give it a key that can delete your whole base. Where the service lets you limit a key to certain actions or tables, do it.

Test data and real data

While building

You press Execute.
You use made-up signups.
Emails go to your own address.

After publishing

It runs on every real signup.
Real people get the email.
Mistakes are public.
Before you publish, send three test signups: a normal one, one with a missing name, and one with an odd email. Fix what breaks.
ActivityYour turnWrite it yourself first, then compare.

Your welcome email arrives saying "Hi undefined". Where do you look, and what is the likely cause?

ActivityBuild stepYour product’s back office

Build the signup workflow

In n8n, build the workflow for a new signup: trigger, save a row, send a welcome message, notify yourself. Test it with three different signups and then publish it.

Done when

Export the workflow as a JSON file and keep it. It goes into your repository later in this unit.

Keep these

  • Start with the trigger and read its output.
  • Add one node, run, check, then add the next.
  • Publish when every node works with odd inputs too.
Previous lessonWhat n8n isNext lessonData between nodes