Real actions without paid APIs: built-in nodes, webhooks and free tiers

The forty-nine dollar quote. Meet Sara. She sells handmade candles online and now runs candle-making workshops on Saturdays. She wants three simple things. A customer fills in a booking form, the booking lands in a spreadsheet, and the customer gets a confirmation email. A vendor quoted her 49 dollars a month for a connector, plus fees for every call to their API, which is just the door one program uses to ask another program for something. For a shop that sells maybe twenty workshop seats a month, that eats the profit. The good news is that n8n can do all three steps for nothing, with tools already in the box.

What you will learn. By the end of this lesson you'll be able to do three things. First, pick the built-in n8n nodes that replace most paid connectors, so your flow talks to email, spreadsheets and other services directly. Second, receive data from any website form with a webhook, which we'll define properly in a moment. Third, look at a service's free tier and work out, with simple arithmetic, whether your client's real monthly volume fits inside it. That last skill is the one that keeps you from promising a client "free" and then surprising them with a bill three months later.

Three free tools in the box. Think of a free automation as a small workshop with three things in it. On the left is the toolbox. These are n8n's built-in nodes, ready-made blocks for email, spreadsheets, web requests and schedules that cost nothing to use. In the middle is the doorbell. That's the webhook, a way for a website to ring your workflow the moment something happens, instead of your workflow checking again and again. On the right is the sample basket. Those are free tiers, the amount of a service a company lets you use without paying. Most small-business automations live happily inside these three.

The toolbox: built-in nodes. Let's open the toolbox. The Send Email node uses SMTP, the standard way mail servers pass messages, so any email account Sara already has can send confirmations or invoices. The Gmail and Google Sheets nodes connect to her own Google account, which is free at her volume. The HTTP Request node is the universal adapter. If a service has a public web address that accepts requests, you can call it without a dedicated connector. And the Schedule Trigger starts a flow on a timer, say every morning at eight for a sales report. The n8n documentation lists every node, so check there before paying for a connector.

The doorbell: what a webhook is. A webhook is a web address that starts your workflow when something sends data to it. Picture a delivery person ringing a shop's doorbell. The shopkeeper doesn't walk to the door every five minutes to check for parcels. That checking would be called polling, asking a service over and over whether anything is new. With a webhook, the form pushes the booking to you the instant it's submitted. In n8n you add a Webhook node and it gives you its own address. You paste that address into the form tool's settings, and from then on every submission rings your workflow.

Worked example: Sara's booking flow. Here's Sara's whole flow. First, a customer opens the workshop page and sees an ordinary booking form. Behind it are three nodes inside n8n: the Webhook, a Google Sheets node, and a Gmail node. Now watch one booking travel. Lina books a seat for Saturday. The form posts her details to the webhook address. The webhook passes them on, the Sheets node appends a new row with her name and date, and then the Gmail node sends her a confirmation. No connector subscription, no per-call fee, and Sara sees every booking in a spreadsheet she already knows.

What the webhook receives. What actually arrives at the doorbell? Usually JSON, a plain text format of labels and their values, like a filled-in form. Here is Lina's booking as the webhook receives it. The Webhook node files the form's details under the label body, next to some technical details we can ignore. Inside body are her name, email, the workshop, the date and the time. You don't need any code to use it. In the email field you write an expression: double curly braces, dollar sign json dot body dot name, and close the braces. You can see it on screen. The word body is there because that is where the form's details sit. n8n swaps the expression for the value, so the email says Hi Lina Haddad. Do the same for the service, date and time, and you get exactly the booking line and greeting Lina would see in her inbox.

The sample basket: will it stay free?. A free tier is the amount of a service you may use before paying, like the free samples a shop hands out. The trap is guessing. So count. At her busiest, Sara expects about one booking a day, which means one email and one spreadsheet row, plus five AI summaries of customer messages. Take each daily count times thirty for a month. Now copy it down the column. Each free tier is measured per service, so compare each row with its own limit, not one grand total. Open each service's pricing page, check thirty emails, thirty rows and a hundred and fifty summaries against their limits, and leave a safety margin for a busy holiday month. A busier client with fifteen bookings a day needs the same sum, just with bigger numbers.

Hosting n8n itself for free. There's one more cost to think about, and that's n8n itself. The self-hosted version is free. You run it on your own computer, a cheap mini PC, or a small server, and the number of workflow runs is limited only by that machine. The n8n cloud plan is easier to set up, but it's paid after the trial. For a client like Sara, a small always-on machine in the back office is often enough. Self-hosting for your own or a client's internal use is free, but check n8n's license before you resell n8n itself as a service. And what about the AI step, the part that usually costs per call? That's next lesson, where Ollama runs a model on that same machine.

Common mistake: the test URL. Here's the mistake almost everyone makes once. The Webhook node shows two addresses, a Test URL and a Production URL. The test one only works while you've clicked listen for a test event in the editor. Builders paste the test address into the form, it works during the demo, and the next morning every booking disappears without an error. Sara's spreadsheet stays empty and customers think they're booked. The fix is simple. Activate the workflow, then paste the Production URL into the form. Then submit one real test booking and check that the row appears.

Exercise: your own booking doorbell. Now it's your turn. Pick a small business you know, a hair salon, a tutor or a candle shop, and build its booking doorbell. Add a Webhook node, then a Google Sheets node that appends the name, email, date and time. Create a simple form with a free form tool that can post to a web address, and send one test booking. Add a Gmail or Send Email node with a personal greeting built from expressions. Finally, activate the workflow, switch the form to the Production URL, and test once more. Bring your monthly volume count to the next lesson.

Recap. Let's pull it together. First, n8n's built-in nodes, like Send Email, Google Sheets, HTTP Request and Schedule Trigger, cover most of what a small business needs without any connector subscription. Second, a webhook is a doorbell for your workflow. The form pushes data the moment it's submitted, and you must use the Production URL on an active workflow. Third, free tiers are real but limited, so multiply daily counts by thirty and compare each service with its own pricing page before you tell a client it costs nothing. That's how Sara got her booking flow for zero dollars a month.