What is n8n and how to build your first workflow

A website form arrives by webhook, a row is added to a sheet, the team gets a notification: building, testing and monitoring your first n8n workflow.

· 12 min readAI

Short answer

n8n is a workflow automation tool that connects apps through nodes; a workflow starts with a trigger, moves through nodes and reaches your accounts through credentials. For a first workflow, receive the form by webhook, add a row to a sheet, send a notification, test with real data and set an error workflow.

A request comes in through the quote form on the website at seven on a Friday evening. It lands in a shared mailbox that nobody opens until Monday morning, and the customer waits two days for an answer. The practical answer to what is n8n sits in exactly that gap: it is a workflow automation tool that connects your apps and turns this kind of manual copying into a workflow that runs on its own. In this article we first cover how n8n works and where it can be hosted, then build a first workflow step by step: it takes a form submission, writes it to a sheet and sends a notification.

If you have not chosen a tool yet, read n8n vs Make vs Zapier first; if you do not know which job to start with, read where to start with automation. Here we assume you have picked n8n.

Cloud or self-hosted

You can use n8n in two ways. According to the n8n documentation, with Cloud n8n manages the infrastructure; with self-hosting you provide and manage it yourself. The table below summarises the part of the documentation’s comparison that matters here.

Topic n8n Cloud Self-hosted
Setup No installation Installation needed with Docker, npm or a server
Technical skill Not required Required for installation and configuration
Maintenance Handled by n8n Your responsibility
Control Managed by n8n; customisation is limited to the available options Full control over deployment and configuration
Speed of starting Start right away Takes longer to set up

Self-hosting can look like the freer route, but the maintenance moves to you. In practice that means keeping the server running, updating n8n, taking backups and securing access are your jobs, and the n8n documentation recommends Cloud for people without technical expertise. If nobody can look after this, building your first workflow in the cloud is the more realistic start. For cases where data control matters and for licence details, see the comparison article above.

The parts of a workflow

Every n8n workflow is made of the same four parts:

  • Trigger. The event that starts the workflow: a form submission, a schedule, an email. In the documentation, trigger operations appear with a bolt icon when you search for a node. Our first workflow starts with the Webhook node.
  • Nodes. The building blocks of a workflow. A node’s operation is either a trigger or an action: it fetches, sends or transforms data.
  • Credentials. The login details a node uses to connect to an account. n8n keeps them as securely stored records, separate from the nodes.
  • Execution. A single run of a workflow. Runs you start by hand in the editor are manual executions; the runs of a published workflow that start on their own are production executions.

You can read what any workflow does by looking at these four: what starts it, which nodes it passes through, which accounts it touches, and where the record of each run is.

Building the first workflow: form, sheet, notification

Our example: the contact form on the site reaches n8n by webhook, the form fields are added to a Google Sheets spreadsheet as a new row, and a notification goes to the team.

  1. Prepare. Create the header row in the sheet: for example name, email, phone, message, time sent. Decide who gets the notification and through which channel (email or a chat app). Also make sure your form can send data to an address; most form tools have a “webhook” or similar setting, and if yours does not, ask whoever built your site.
  2. Add the Webhook node. In an empty workflow choose “Add first step” and select the Webhook node. Set the HTTP method to the one your form sends (usually POST). In the Path field n8n generates a random path; leaving it random avoids conflicts, and you can type a fixed path if you want one.
  3. Use the test URL. The Webhook node has two addresses: test and production. According to the documentation, the test address is registered when you select “Listen for test event” or run the workflow while it is not active, and it shows the incoming data in the workflow. Make the test address the form’s target, make a real submission on the site and check that the fields appear in the node.
  4. Connect the Google Sheets node. After the webhook, add the Google Sheets node and choose “Append Row”. Create a credential to connect the account; n8n recommends OAuth2 for Google. On n8n Cloud you can sign in with Google directly for some Google nodes (managed OAuth2); when self-hosting you need to set up your own OAuth2 credentials in the Google Cloud Console. Then map each incoming field to a sheet column one by one.
  5. Add the notification node. For email, add the Send Email node, or the node for the chat app you use. Put the form fields into the message text: who wrote, what they want, their phone number.
  6. Test with real data. Run the workflow from start to finish by hand and check the row in the sheet and the notification. The table below shows which tests to run.
  7. Switch to the production URL and publish. Change the form’s target to the production URL and publish the workflow. According to the documentation, n8n does not show incoming data in the editor on the production address; you follow the runs in the workflow’s Executions tab.
  8. Connect an error workflow. It is described in the next section; set it up before you publish the first workflow.
First n8n workflow: a form arriving by webhook, a Google Sheets row, a notification, credentials and an error workflow Main workflow Webhook: form arrives Google Sheets: add a row Send a notification Test URL, then production URL Credential: Google account Credential: alert account Error workflow Main workflow fails Error workflow: Error Trigger Named person is notified First n8n workflow: a form arriving by webhook, a Google Sheets row, a notification, credentials and an error workflow Main workflow Webhook: form arrives Google Sheets: add a row Send a notification What each step connects to Test URL, then production URL Credential: Google account Credential: alert account Error workflow Main workflow fails Error workflow: Error Trigger Named person is notified
Figure: The form arrives by webhook, a row is added to the sheet and a notification goes out; if the workflow fails, a separate error workflow tells a named person.

The real submission in step 3 matters more than it seems: a workflow that works with sample data may not work with the field names your form actually sends. The tests below list typical problems you can catch before going live.

Test What to check
Fill in and really submit the form Do the field names match the sheet columns
A long message with Turkish characters Do the characters reach the sheet and the notification intact
An optional field left empty Is the row still written, does the notification break
Submit the same form twice Do two rows appear, and is that what you want
Rename a column in the sheet Does the workflow quietly write to the wrong column, or fail

Make sure you hear about errors

One day the workflow stops: the Google connection expires, the sheet is deleted, the form sends data in a different shape. Without an error workflow nobody tells you, and you notice weeks later that no rows were added.

According to the n8n documentation, you can set an error workflow in each workflow’s settings; it runs when the workflow fails. To set it up:

  1. Open a new workflow and add the Error Trigger as the first node.
  2. Name it something like “Error Handler”, save it, and add an email or chat notification node after it; put in the message which workflow stopped, at which node and with what error message.
  3. In the main workflow, open Options > Settings, select this workflow in the Error workflow field and save.

Two details in the documentation matter. You cannot test an error workflow by running a workflow by hand. The Error Trigger runs only when an automatic execution fails, so to try it you need to make the published workflow fail on purpose (the documentation mentions the Stop and Error node for this). You can use the same error workflow for several workflows. Sending the notification to a team address keeps it from going nowhere when one person is on leave; still, make one named person responsible for looking at the error, because a notification sent to everyone is owned by no one.

Keeping credentials safe

As the workflow runs it reaches the sheet, the mailbox and perhaps the CRM; the credentials that grant this access are the most sensitive part of it.

  • Create a credential, do not paste the key into a box. n8n stores credentials as records separate from the nodes. Do not write keys into an Edit Fields or Code node, into workflow notes or into descriptions shared by email.
  • Give them meaningful names. The documentation suggests naming credentials with the app, the type and the purpose. A name like “Google Sheets, sales sheet, append only” tells you six months later what is connected to what.
  • Limit the allowed domains for HTTP Request. The “Allowed HTTP Request Domains” field, found on many credentials, controls which domains a credential may be used against; it prevents the credential from being sent to the wrong address by mistake.
  • Do not leave the webhook address unprotected. The Webhook node can require authentication such as Basic auth, Header auth, JWT or n8n user auth, and you can also allow only certain IP addresses. Even for a simple form, asking for a secret header value stops anyone who learns the address from writing rows into your sheet. If your form cannot send a custom header, talk to whoever built your site.
  • Keep access narrow. Connect to the sheet with an account created only for this workflow, not with a personal account that can reach your whole Drive. When someone leaves the team, reconnect the credential.

When not to automate

Not every job deserves a workflow. Do not build one, or wait, when:

  • The job happens a few times a month and takes minutes by hand; maintaining the workflow would cost more than it saves.
  • The process has not settled. If you automate a job that runs differently each time, you automate its exceptions too.
  • A mistake is costly and nobody checks: for messages to customers, payments and invoices, start with a notification and move forward with human approval.
  • Nobody will take ownership of the error notification.

To choose which job is next, the order in where to start with automation helps; for examples from other processes, see business process automation examples.

Common mistakes

  • Testing only with the test URL. The test address works while the workflow is not active; if you forget to switch the form to the production address, live submissions go nowhere.
  • Settling for sample data. Field names, empty fields and Turkish characters only show up in a real submission.
  • Leaving the error workflow until last. The workflow is live, but if it stops, nobody is told.
  • Connecting everything with one account. If one credential leaks, access to everything goes with it.
  • Naming no owner. When the person who built the workflow leaves, nobody knows who looks after it. Put an owner and a short note in the workflow’s name.
  • Adding an AI step too early. A step that summarises or classifies the message can come later; first make the basic workflow reliable. We touch on this in how to set up an AI assistant chatbot.

Common questions

Do I need to write code to use n8n?

Not for the workflow in this article: you pick nodes and map fields. Where ready-made nodes are not enough, n8n has a Code node, but you do not need it for a first workflow.

What is the difference between the test URL and the production URL?

According to the documentation, the test address works when you select “Listen for test event” or run the workflow, and it shows the incoming data in the editor. The production address is registered when you publish the workflow; data is not shown in the editor, and you follow the runs in the Executions tab.

Can anyone who learns the webhook address run my workflow?

If you have not chosen authentication, yes. The Webhook node offers Basic auth, Header auth, JWT and n8n user auth, and an IP allowlist can be set as well. Choose the method your form supports.

If you want to try this on your own today, do this: if you have no n8n account, open one on Cloud and add a Webhook node to an empty workflow. Then make a real submission to the form’s test address and write down on a sheet of paper which field names arrive in the node. That list will be your only source for the sheet’s columns and the notification text. If you would rather have the workflow built and looked after than build it with your own team, our automation and AI service covers that. If you are choosing an agency, the questions in how to choose an automation agency will help.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.