These three workflows are starting points, not finished products. Each one is built to be imported into your own n8n, wired up to your accounts, and then changed to fit how you actually work. Treat them as a first draft you edit, not a machine you flip on and forget.
Here's the simple version: n8n is a tool that visually connects apps together so they interact automatically. You can self-host it or use their cloud tiers to start with a 14-day free trial that's generous enough to feel what the tool can actually do before committing anything financially. If you've never opened it before, create an account first, then come back here. The three workflows below are meant to be imported once you have a workspace to drop them into, not built from scratch.
Start a free n8n trial →New Lead Notifier
If you refresh your inbox to see whether a new lead came in, this is for you. It watches your contact form or a webhook, and the moment someone submits, it sends you a tidy notification with their details. The message lands in Slack or your email instead of you going to check. You find out when it happens, not twenty minutes later.
This one fits anyone who captures leads and hates the lag between "someone reached out" and "I noticed." Speed on a fresh lead matters, and this closes the gap.
- A form or webhook that can send data out when someone submits. Most form tools support this.
- A Slack workspace where you can add an app, or an email account you can send from.
- Permission to connect that Slack or email account inside n8n.
The incoming data. When your form fires, it sends a bundle of fields, and the field names are rarely what you expect. Submit a test entry first and look at exactly what comes through. Once you can see the real field names, mapping them into your notification message is quick. People who skip the test submission spend an hour confused about why their message says "undefined."
Submission Logger
If you copy form responses into a spreadsheet by hand, stop doing that. This workflow takes each new submission and adds it as a fresh row in a Google Sheet automatically. Same trigger as the notifier, different ending. Every response gets logged, in order, without you touching it.
This fits anyone building a list, a tracker, or a simple record of who filled out what. It's the quiet backbone workflow. Boring, and worth it, because manual copy-paste is where small errors creep in and time is wasted.
- The same form or webhook that sends data on submission.
- A Google account with access to Google Sheets.
- A sheet already created, with column headers that match the fields you plan to log.
The column mapping. n8n needs your sheet columns and your form fields to line up, and it helps a lot to set up the header row before you connect anything. Decide your columns first, then map each field to one. If you add a new form field later, remember the sheet won't grow a column on its own. You have to add it and update the mapping, or that data quietly goes nowhere.
Scheduled Digest
If you check three places every morning to piece together how things are going, this saves you the rounds. Instead of a trigger that fires on an event, this one runs on a clock. Daily or weekly, whichever you set. It pulls data from a source, compiles it into a short summary, and sends that summary to Telegram or your email. You open one message instead of five tabs.
This fits anyone who wants a recurring update and keeps forgetting to go look for it. The update comes to you, on schedule, in one place.
- A data source the workflow can read from. This might be a sheet, a database, or an API, depending on what you're summarizing.
- A Telegram bot and your chat ID, or an email account you can send from.
- A rough idea of what a useful summary looks like, so you know what to compile.
The schedule itself, and specifically your time zone. n8n runs on the time zone it's configured with, which is not always the one you live in. If your digest shows up at 4 a.m., the schedule is fine and the time zone is off. Check that setting before you assume the workflow is broken. The second thing beginners underestimate is deciding what to include. A digest with everything in it is as useless as no digest. Pick the few things you'd actually act on and leave the rest out.
These three cover the most common reasons people start automating: knowing sooner, logging without touching it, and checking less often. They're deliberately simple. Once one of them is running and you trust it, the real unlock isn't more workflows, it's noticing the next repetitive thing you do and asking if it belongs in n8n too. If you're not sure which one to build first, that's a different question, and we've got a guide for that: How to Pick Your First AI Automation.