The 30-second overview
| Item | Details |
|---|---|
| What you build | An automation that runs on its own |
| How long it takes | About 30 minutes the first time |
| Any coding needed? | No |
| Three core concepts | Triggers, nodes, credentials |
| Most common sticking point | Forgetting to set the workflow to Active |
Before you start: what you need
This tutorial walks you through building a practical automation on n8n: when a form or a schedule fires, automatically write the data into Google Sheets and send a notification. Before you begin, confirm that:
- You already subscribe to the n8n standard plan on RoamerHost (if not, start with plans and pricing).
- Deployment has finished and your dedicated subdomain and SSL have been issued.
- You have the account for the service you want to connect ready (this tutorial uses a Google account as the example).
Not sure what n8n is yet? Read "What is n8n? A complete introduction to the workflow automation platform" first, then come back and build.
Step 1: log into the dashboard and open the n8n editor
First, get into your n8n environment:
- Open a browser and log into the RoamerHost dashboard.
- Find your n8n instance in the service list and confirm its status is "Running".
- Click the instance's dedicated subdomain (in the form
your-name.roamerhost.com) to open the n8n editor. - The first time you enter, follow the on-screen steps to create your n8n administrator account and password. Keep this password safe, as you will use it every time you log into the editor.
Forgot your n8n password? You can request a reset from the dashboard, or contact Support for help.
Step 2: get to know the editor and create a new workflow
After logging in you land on the n8n main screen. A few key concepts to establish first:
- Workflow: one complete automation, made up of multiple nodes.
- Node: one step in the flow, such as a trigger, reading data, or sending a message.
- Canvas: the workspace where you drag and connect nodes.
To create a new workflow:
- Click "+" or "Create Workflow" in the top right to create a new blank workflow.
- An "Add first step" prompt appears in the center of the screen, which is where your first node goes.
- Name the workflow now (for example "Form notification") to make it easier to manage later.
Step 3: add a trigger node
Every workflow needs a trigger that decides "when execution begins". After you click "Add first step", n8n lists the available trigger types. The common ones:
| Trigger type | What it does |
|---|---|
| Manual Trigger | Runs when you click it, good for testing |
| Schedule Trigger | Runs on a schedule (for example every day at 9am) |
| Webhook | Fires when an external HTTP request arrives (forms, third-party services) |
| App Trigger | Fires on a specific app event (for example a new email in Gmail) |
To make testing as you build easier, do this for now:
- Choose "Manual Trigger" as the starting point.
- The node appears on the canvas, and that is the entry point of your flow.
You can swap the Manual Trigger for a Schedule or Webhook trigger at any time to let the flow run on its own. Webhooks are covered in detail in the advanced tutorial.
Step 4: add an action node and set up credentials
Now add the first "action", writing the data into Google Sheets:
- Click the "+" to the right of the trigger node, then search for and select "Google Sheets".
- For the operation, choose "Append Row".
- The system asks you to set up a credential. Click "Create New Credential" and follow the prompts to authorize with your Google account, so n8n has permission to write to your spreadsheet.
- Once authorization is done, pick the spreadsheet file and the sheet to write into.
- In the field mapping area, fill in the content you want written, for example the
NameandTimefields.
A credential only has to be set up once, and other nodes for the same service can reuse it. All credentials are stored securely in your own isolated data volume.
Step 5: chain a second action (send a notification)
Once the data is written, add another node to send a notification and make the flow complete:
- Click the "+" to the right of the Google Sheets node, and this time pick the messaging tool you use, for example "Slack" or "Telegram".
- Choose "Send Message" as the action.
- Set up and authorize the credential for that service in the same way.
- In the message body you can reference data from the previous node directly. Click the variable button next to the field and pick a field from the previous step (for example pulling the name into the message text).
Your flow is now: manual trigger → write to Google Sheets → send a notification, three nodes in a line.
Step 6: test your workflow
Do not rush to go live. Always run a test first to confirm each node works:
- Click the "Test workflow" / "Execute Workflow" button at the bottom of the screen or in the top right.
- n8n starts from the trigger and executes each node in order.
- Nodes that succeed light up with a green check. If one turns red, open it and read the error message (usually a credential that was not authorized properly, or a field filled in wrong).
- Check Google Sheets to confirm the data was written, and check that the notification arrived.
Make good use of each node's "Output" panel, which shows the data actually being passed along. It is the single most important debugging tool.
Step 7: activate the workflow so it runs automatically
Once the tests pass, you can go live:
- Swap the trigger from Manual Trigger to a Schedule Trigger or Webhook (a manual trigger cannot run automatically). For example, set it to run every day at 9am.
- Flip the "Active" switch in the top right to the on position.
- Save the workflow. Once active, n8n stands by 24/7 on RoamerHost and runs automatically when the time comes or the condition is met.
Because your n8n runs in an isolated container on RoamerHost with automatic restart enabled, the flow keeps running even if you close your browser or shut down your computer.
Next steps
Congratulations on finishing your first automation. Next you can try:
- Swapping the trigger for a Webhook so an external website form triggers the flow directly.
- Adding conditional logic (an IF node) so the flow branches based on the data.
- Installing community nodes to connect to more niche services.
These advanced techniques are all covered in "n8n webhooks and third-party integration guide". If you run into trouble along the way, Support is always there.
FAQ
Q: Testing works, but nothing runs in production. Why?
Nine times out of ten you forgot to set the workflow to Active. Testing uses the Test URL and manual execution, while production requires activating the flow and switching to the Production URL. This is the single most common beginner question.
Q: How do I set up credentials?
A credential is the API key or authorization for a service, managed centrally in n8n and shared across workflows. Set a naming convention from the start, because once you have a lot of flows you will not be able to tell which credential belongs to which account.
Q: How do I investigate a failed run?
Look at the execution log, which shows what each node received and what it produced. Work backwards and find the first node whose output does not match expectations, and that is where the problem is.
Q: Can it run on a schedule?
Yes, with the Schedule Trigger. Watch your time zone setting, which is the most common reason a schedule does not run when expected.
Q: What should I learn next?
It depends on what you need. For real-time triggering from external services, see the webhook guide; for storing data, see n8n plus NocoDB; if it gets slower over time, see execution data growth.
Sources and further links
n8n's nodes and pricing change often. These are the primary sources for checking:
- n8n official documentation
- n8n official pricing — cloud plans and quotas
- n8n source code and release notes — the authoritative source for license terms
Further reading
- n8n AI Agent guide: building automations that use tools on their own
- n8n gets slower over time: execution data growth and cleanup
- n8n plus NocoDB: keep your automation data in your hands
- n8n FAQ: resource limits, webhook URLs, and community nodes
Want someone to build it for you?
If you would rather not assemble these workflows yourself, or the project is large enough that you want someone planning it with you, Roamer Tech (the company behind RoamerHost) takes on contract work for business process automation and AI agents: