Build Your First AI Automation: From Enquiry to Follow-Up (n8n, Step by Step)

A customer fills in a form, and a few seconds later it's logged in Google Sheets, the customer has a personal reply, and your team has an alert. Here's how to build it in n8n, click by click, including the Google setup and the real errors we hit. WHY DO COMPANIES AUTOMATE THIS? Because the same small job happens all day: read the message, copy it into a sheet, write back, tell the team. An automation does that the same way every time, in seconds. In our test run the whole chain took 8.6 seconds, from form to reply. Nobody copied anything and no message was left sitting in an inbox. The trade-offs are real too. You have to set it up and look after it. Ours hit a busy AI model, and the Google connection has to be re-approved about once a week while the app is in testing. So we show you how to make it retry and what to check when it breaks. WILL AI REPLACE JOBS? Look at what this build actually does. It takes the repetitive part, the logging and the first reply, and hands the real problem to a person, with a summary already written. The order still has to be found and the refund still has to be checked. That's the kind of automation we teach on this channel. IS AI AUTOMATION HARD TO LEARN? Not this kind. If you can fill in a form and drag a field from one box to another, you can follow this. Every click is on screen, including where to find things in Google Cloud. The tools we use have free tiers. What you'll build (six nodes): 1. On form submission: a Contact us form with three required fields 2. Clean the fields: trim spaces, lowercase the email 3. AI: read the enquiry: Information Extractor and a free Gemini model pick the intent and write a one-sentence summary 4. Log to Google Sheets: append a row 5. Email the customer: a personal Gmail reply 6. Notify the team: a Gmail alert with every detail Also covered: the Google Cloud project, enabling the Sheets, Drive and Gmail APIs, the consent screen and test users, the OAuth client and redirect URL, a real "Error 403: access_denied" and its fix, why we stay in Testing (you reconnect about every 7 days), Retry On Fail after a real "Service unavailable" from Gemini, reaching back to earlier nodes, and test URL versus production URL. CHAPTERS 0:00 What you'll build 0:35 What you need, and the six steps 1:18 Google Cloud console: project and APIs, click by click 2:51 Consent screen and test users 3:45 Creating the OAuth client 4:50 Connecting n8n, and a real 403 5:53 Why we stay in Testing, and the sheet 6:31 Node 1: the form trigger 7:32 Node 2: clean the fields 8:27 Node 3: the AI step 9:23 A real failure: Retry On Fail 10:22 Node 4: log to Google Sheets 11:31 Node 5: email the customer 12:29 Node 6: notify the team 13:24 The full test, with messy input 14:17 Going live: publish and executions 15:26 Recap and your next step SOURCES n8n Form Trigger: https://docs.n8n.io/integrations/buil... n8n Information Extractor: https://docs.n8n.io/integrations/buil... n8n node settings (Retry On Fail): https://docs.n8n.io/workflows/compone... Google OAuth 2.0 (Testing tokens expire in 7 days): https://developers.google.com/identit... ABOUT THE DEMO Everything on screen was built and run for real in a self-hosted n8n on our own server on 18 October 2026, with the channel's own Google account. Names are sample data. Emails went to test addresses in our own inbox. Private details such as the client secret and the account email are blurred. One screen, the Google 403 page, is recreated from the exact text Google showed us, because it appeared in a sign-in pop-up we didn't capture. The narration is a synthetic voice. PREVIOUS: AI Automation Roadmap for Beginners: 5 Stages, in Order NEXT: Agentic AI Roadmap for Beginners #n8n #aiautomation #workflowautomation