Ready-to-import n8n templates

Every message from your website form reaches n8n, gets validated (valid email, no spam, no repeats), is saved as a row in your Google Sheet and you get an email alert you can reply to directly. No paid plugins or external services.

You need: n8n (self-hosted or n8n Cloud) with a public address, a Google account with the sheet and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Prepare the sheet: a tab with the headers date, name, email, phone, message, page in the first row.
3. Connect the accounts: a Google Sheets credential in Save to sheet and an SMTP credential in Email me.
4. Edit the Config node: sheet ID, tab, your email and your time zone.
5. Turn the workflow on with the Active switch and copy the Production URL of the Web form node. In its options, under Allowed Origins, enter your site address (for example https://yourdomain.com).
6. Paste the form on your website (WordPress: Custom HTML block) and replace the URL:

<form id="contacto">
  <input name="name" placeholder="Name">
  <input name="email" type="email" required placeholder="Email">
  <input name="phone" placeholder="Phone">
  <textarea name="message" required placeholder="Message"></textarea>
  <input name="website" style="display:none" tabindex="-1" autocomplete="off">
  <button>Send</button>
</form>
<script>
document.getElementById('contacto').addEventListener('submit', async (e) => {
  e.preventDefault();
  const data = Object.fromEntries(new FormData(e.target)); data.page = location.href;
  const r = await fetch('PASTE_THE_PRODUCTION_URL_HERE', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify(data) });
  const j = await r.json();
  alert(j.ok ? 'Thanks! We will get back to you soon.' : 'Could not send: ' + j.message);
  if (j.ok) e.target.reset();
});
</script>

The website field is hidden: people do not see it and bots fill it in, so they are discarded. The same email cannot send more than one message every 10 minutes.

Every day at 8:00 it reads your appointments in Google Sheets and emails a reminder to every client with an appointment the next day. Fewer no-shows, no manual messages. Each appointment is reminded only once and you get a summary of what was sent.

You need: n8n (self-hosted or n8n Cloud), a Google account with the sheet and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Prepare the sheet: a tab with the headers date, time, name, email, service, cancelled in the first row. One row per appointment; write yes in cancelled to skip it.
3. Connect the accounts: a Google Sheets credential in Read appointments and an SMTP credential in Send reminder.
4. Edit the Config node: sheet ID, business name, the closing text (address, how to cancel), date format, time zone and emails.
5. Test: add an appointment for tomorrow with your email and click Execute workflow: the reminder should arrive. Then turn the workflow on with the Active switch.

To avoid repeated reminders, n8n remembers what was sent only in automatic runs; manual tests send again.

On weekdays at 9:00 it checks your invoices in Google Sheets and writes to each client: a friendly notice 3 days before the due date and notices 1, 7 and 15 days after it is overdue, each one firmer. When you mark the invoice as paid, it stops. You get a daily summary of what was sent.

You need: n8n (self-hosted or n8n Cloud), a Google account with the sheet and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Prepare the sheet: a tab with the headers invoice, client, email, amount, currency, due_date, paid in the first row. Write yes in paid when you get paid.
3. Connect the accounts: a Google Sheets credential in Read invoices and an SMTP credential in Send notice.
4. Edit the Config node: sheet ID, company name, how clients pay you, the notice days, date format, time zone and emails.
5. Test: add an invoice due in 3 days with your email and click Execute workflow: the notice should arrive. Then turn the workflow on with the Active switch.

Each notice goes out only once per invoice (n8n remembers it in automatic runs; manual tests send again).

Lead follow-up by email

Every day at 10:30 it checks your leads sheet and sends each lead the next email of a 3-step sequence, with the waiting days you choose. Every email includes an unsubscribe link: if someone clicks it, they are marked and get no more emails.

You need: n8n (self-hosted or n8n Cloud, with a public URL for the unsubscribe link), a Google Sheet and an email account to send from (SMTP).

1. Set up the sheet: a tab named Leads with these columns in row 1: email, name, signup_date, step, last_sent, unsubscribed. Add your leads with email, name and signup date (the workflow fills in the other columns).
2. Import the workflow: in n8n, Workflows → Import from file.
3. Connect Google Sheets: create a Google Sheets OAuth2 credential and select it in the 3 sheet nodes.
4. Connect email: create an SMTP credential and select it in Send email.
5. Edit the Config node: sender, sheet ID, the production URL of the Unsubscribe (webhook) node (shown when you open it), a secret phrase and the text of the 3 emails.
6. Test it with a lead of your own (Execute workflow) and click the unsubscribe link in the email you get. If everything works, activate the workflow.

Only email people who gave you their address: complying with your country's privacy and anti-spam laws is your responsibility.

Reads the email list in your Google Sheet and writes the result for each address in another tab: valid, invalid, duplicate or review, with the reason. It detects invalid format, duplicates, typos in Gmail/Hotmail/Outlook/Yahoo (and suggests the right one), temporary addresses and domains that cannot receive email. It sends nothing to your contacts and uses no paid services: DNS is queried on Google's public DNS.

You need: n8n (self-hosted or n8n Cloud) and a Google account with the sheet.

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Connect Google Sheets: create a Google Sheets credential and choose it in the Read sheet and Save result nodes.
3. Prepare the sheet: your list with an email column (or the name you set in Config) and an empty tab for the result, with the headers email, status, reason, suggestion, checked in the first row.
4. Edit the Config node: the sheet ID and the tab names.
5. Run it with Execute workflow. A list of 1,000 emails takes 1–3 minutes (one DNS query per distinct domain).

Before a campaign, send only to the valid ones; the ones marked review are worth a quick manual look. Fewer bounces protect your domain's reputation.

Weekly Instagram report

Every Monday at 9:05 you get an email with each account's followers (and how much they changed), the week's posts, likes and comments, and the best performing post.

You need: n8n (self-hosted or n8n Cloud), an Instagram Business or Creator account linked to a Facebook page, and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the .json file you downloaded.
2. Connect Meta: create an app at developers.facebook.com (Business type), add the Instagram Graph API and generate a long-lived page access token with the instagram_basic and pages_show_list permissions. In n8n create a Facebook Graph API credential with that token and select it in the IG Cuenta node. Your Instagram account ID shows up in the Graph API Explorer by requesting me/accounts?fields=instagram_business_account.
3. Connect email: create an SMTP credential and select it in the send node.
4. Edit the Config node: your accounts, the sender email and the recipient.
5. Test it: click Execute workflow. If the email arrives, turn on the Active switch.

The Meta token lasts about 60 days: when it expires, generate a new one and update the credential. Since you use your own app with your own accounts, Meta app review is not required.

Auto Post AI (Instagram, Facebook and LinkedIn)

Every 2 days at 19:00 it builds a new post per brand: text that combines your phrases without repeating, an AI-generated image (with a backup photo if it fails), and publishes it to Instagram, your Facebook page and, optionally, LinkedIn. When it finishes it emails you a summary and warns you before the Meta token expires.

You need: n8n (self-hosted or n8n Cloud), Ollama with the llama3.2:1b model (free; it describes the image), an Instagram Business account linked to a Facebook page and an email account for alerts (SMTP). LinkedIn is optional.

1. Import the workflow: in n8n, Workflows → Import from file.
2. Connect Meta: create an app at developers.facebook.com (Business type), add the Instagram Graph API and generate a long-lived token with instagram_basic, instagram_content_publish, pages_show_list, pages_read_engagement and pages_manage_posts. Create a Facebook Graph API credential in n8n and select it in the Instagram Contenedor ID, Publish and Get Page Token nodes.
3. Connect Ollama: install Ollama, run ollama pull llama3.2:1b and create an Ollama credential in n8n pointing to your server (for example http://localhost:11434).
4. Email and LinkedIn: an SMTP credential in Send Email. For LinkedIn, a LinkedIn OAuth2 credential in LinkedIn Post and your page ID in Config; if you do not use it, delete the 3 LinkedIn nodes.
5. Edit the Config node: your brands, IDs, tone, phrases (the more you add, the less it repeats) and the token date.
6. Test it with Execute workflow and check your accounts. If everything looks good, activate it.

Images come from Pollinations (free) and, if that fails, from Unsplash. Make sure the content follows Instagram and Facebook rules: what gets published is each account's responsibility.

Every day at 9:00 it tests your Meta token against the Graph API and emails you only when needed: if the token stopped working, when the expiry date gets close (30, 14, 7, 3, 1 and 0 days before) and on any fixed reminders you add.

You need: n8n (self-hosted or n8n Cloud), the Facebook Graph API credential your other workflows already use and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Connect Meta: in the Test token node choose your Facebook Graph API credential (the one you post with).
3. Connect email: create an SMTP credential and choose it in the Send alert node.
4. Edit the Config node: the token expiry date (shown in Meta's Access Token Debugger), the alert days, your time zone and the emails.
5. Test: briefly set token_expires to today's date and click Execute workflow: the alert should arrive. Put the real date back and turn the workflow on with the Active switch.

If Meta ever revokes the token (password change, removed permissions), the alert arrives that same morning, before your posts fail.

Every 10 minutes it checks your sites from the outside and emails you only when something changes: the site is not responding (and again when it is back), the SSL certificate is invalid or about to expire, the domain does not resolve or cannot receive email. No paid services or keys: it uses Google's public DNS and the public certificate log crt.sh.

You need: n8n (self-hosted or n8n Cloud) and an email account to send from (SMTP; Gmail with an app password works).

1. Import the workflow: in n8n, Workflows → Import from file and pick the downloaded .json.
2. Connect email: create an SMTP credential and choose it in the Send alert node.
3. Edit the Config node: your sites, the certificate alert days and the emails.
4. Turn the workflow on with the Active switch. Important: the monitor remembers each site's state between runs so it does not repeat alerts, and n8n only keeps that state in automatic runs (not when testing by hand).
5. Test: briefly add a domain that does not exist to sites (for example does-not-exist-123.com): the alert arrives within 20 minutes. Then remove it.

Downtime alerts go out from the 2nd failure in a row, so a few seconds of downtime do not trigger them. If you prefer Telegram or Slack, replace the email node: the text comes in subject and body.