FR Newsletter

AI for Work

Your first automation: send every new lead to a spreadsheet

A new lead fills in your contact form. Then what? Too often, the message sits in an inbox and gets lost. Your first automation can fix that in an afternoon: every submission lands as a new row in a spreadsheet, and you get a notification. Here is how to build it with Zapier (no code) or n8n (open source).

Trigger, action: the only two words you need

Every automation follows the same pattern. A trigger is the event that starts it: Zapier defines it as "an event that starts a Zap". Then one or more actions run, one after the other. In our case:

  1. Trigger: a new form submission.
  2. Action 1: add a row to a spreadsheet.
  3. Action 2: send you a notification (email or chat message).

Before you open any tool, prepare your spreadsheet: one sheet, a first row with clear column names (date, name, email, message, source). The automation will fill the rows below.

Screenshot coming after our hands-on test
Screenshot of the finished workflow in Zapier and n8n: coming after our hands-on test.

1. Decide which fields you really need

Before building anything, look at your form. The GDPR principle of data minimisation is simple: collect only what you need for the purpose. To call someone back, you rarely need a date of birth or a postal address. Fewer fields also means fewer people who give up halfway, and less sensitive data sitting in a shared spreadsheet.

Add a short sentence under the form that says what you will do with the data and who to contact to have it deleted.

2. Build it with Zapier

Zapier's help center describes the steps for the trigger: from your account, click + Create, then Zap workflows. In the trigger step, pick your form app, choose the trigger event (for example a new submission), and connect your account. Fill in the fields in the Configure tab.

Then add an action: pick your spreadsheet app, choose an event that creates a row, select your file and sheet, and map each column to a field from the form (the email column receives the email field, and so on). Add a second action for the notification.

You can use an assistant to write the notification text:

Write a short notification message for a new lead from my website form. Use these fields: [name], [email], [message]. Two lines maximum, then the link to the spreadsheet.

3. Build it with n8n

In n8n, each step is a node. n8n even has its own form: the n8n Form Trigger node starts a workflow when someone submits a form and generates the form page for you. If you already have a form elsewhere, use the trigger for that app instead.

Chain the nodes: the trigger, then a spreadsheet node that adds a row (map each column to a form field), then a node that sends your notification. The logic is the same as in Zapier, only the vocabulary changes.

4. Test before you go live

Never switch on an automation you have not tested. In Zapier, the Test tab of the trigger has a Test trigger button that loads "a representative sample of the step's data". Submit your form once yourself first, so the sample is a real one, then test each action and check that the row lands in the right columns.

n8n separates two addresses for its form. The test URL shows the incoming data in the editor while you build. The production URL only works once the workflow is saved and published, and n8n does not display that data in the workflow: you review it in the Executions tab.

Test the edge cases too: an empty optional field, an accent in a name, a very long message.

5. Plan for errors

An automation will fail one day: an expired connection, a renamed column, a deleted file. The danger is not the error, it is the error nobody sees.

  • Zapier sends error notifications to your Zapier account email by default. You can choose the frequency (immediately, hourly summary, or never, which Zapier does not recommend).
  • n8n uses an error workflow: create a separate workflow that starts with the Error Trigger node, then select it as the error workflow in the settings of your main workflow. Note from the docs: you cannot test it by running the workflow manually, it only runs when an automatic execution fails.

Also keep the form's own copy of submissions (most form tools keep one) as a backup while you gain confidence.

6. Protect the spreadsheet

Your spreadsheet now contains personal data. Share it only with the people who call leads back, never with a public link. Decide how long you keep a lead who never answered, and delete old rows regularly. If someone asks you to delete their data, remember it may exist in three places: the form tool, the spreadsheet and your notification emails.

What to watch

  • Plans and limits change. Both tools have usage limits that depend on the plan. Check the official pricing pages before you rely on a volume.
  • Interfaces move. Button names in this guide come from the official documentation at the time of writing.
  • Where the data goes. With Zapier, your leads pass through Zapier's servers. With n8n, they pass through wherever your n8n instance runs. Mention it in your privacy notice.

Tools in this guide

Questions

Zapier or n8n: which one should I start with?

Zapier is built for people who do not want to manage any software. n8n is open source: it gives more control but usually asks more setup. For a first automation, pick the one you will actually maintain.

Do I need to know how to code?

No. Both tools let you build this workflow by choosing an app, an event and fields to map. Code only becomes useful for unusual cases.

Is it legal to store leads in a spreadsheet?

It can be, if you collect only what you need, tell people what you do with their data, protect access to the file and delete old entries. Under the GDPR, a spreadsheet of leads is personal data like any other.

Sources

  1. Zapier Help Center, Set up your Zap trigger
  2. Zapier Help Center, Manage notifications when errors occur in Zap workflows
  3. n8n Docs, n8n Form Trigger node
  4. n8n Docs, Error Trigger node
  5. General Data Protection Regulation (EU) 2016/679, Article 5 (data minimisation), EUR-Lex