Build a Lead-Rescue Automation in n8n

Capture leads, log them to Sheets, and send timed follow-up emails automatically.

Introduction

30 Second Summary

Every business loses potential customers the same way. Someone fills out a contact form, nobody responds for hours, and the lead moves on to a competitor.

In this project, you will build a lead-rescue automation using n8n. Your workflow captures contact form submissions, logs them in Google Sheets, sends instant email alerts, and queues a timed follow-up so no lead ever goes cold.

What You'll Build

Submit a test lead through your contact form and watch the details appear in your spreadsheet, a notification land in your inbox, and a follow-up email send itself on schedule.

By the end of this project, you'll have:

A branded contact form that captures leads and automatically logs every submission as a new row in your Google Sheets "Lead Tracker" spreadsheet.
An instant Gmail notification that alerts the business owner within seconds of a new lead arriving.
A timed follow-up email that sends itself to the lead after a configurable delay, so no inquiry goes unanswered even when the business owner is busy.
Secret Mission: Add IF branching so urgent leads get an immediate personalized response while normal leads follow the standard timed follow-up.

Are there any prerequisites?

This project builds on your n8n instance from a previous project. You need n8n self-hosted and running, plus a Google account with Gmail.

Before We Start

Before we dive in, let's lock in what you're about to build and why it matters for your freelancing toolkit.

Set Up Google Cloud Credentials

Your workflow will log leads into Google Sheets and send emails through Gmail. For n8n to access these Google services, it needs explicit permission from your Google account.

In this step, you will create a Google Cloud project, enable the required APIs, and set up OAuth2 credentials. You will also create the spreadsheet where every lead will be logged.

In this step, get ready to:

Create a Google Cloud project and enable the Sheets, Gmail, and Drive APIs.
Configure OAuth2 credentials and connect them to n8n.
Create a Lead Tracker spreadsheet in Google Sheets.

Create a Google Cloud project and enable APIs

Google Cloud is Google's platform for managing APIs and services. You need a Google Cloud project to generate the credentials that allow n8n to connect to Google Sheets and Gmail.

Open your browser and go to console.cloud.google.com.
Sign in with your Google account.
Click Select a project at the top of the page, then click New Project.
Enter n8n Lead Rescue as the Project name.
Click Create.
Wait a few seconds for the project to be created, then select it from the project picker at the top of the page.

You should see the project dashboard with n8n Lead Rescue displayed at the top.

Now you need to enable three APIs so n8n can interact with Google Sheets and Gmail.

In the left sidebar, click APIs & Services.
Click Library.
Search for Google Sheets API and click on the result.
Click Enable.
Click the back arrow to return to the Library.
Search for Gmail API and click Enable.
Return to the Library one more time. Search for Google Drive API and click Enable.

Why do we need the Google Drive API?

The Google Sheets integration in n8n requires the Google Drive API in addition to the Google Sheets API. Without it, n8n cannot access your spreadsheets.

To confirm all three APIs are enabled, click Enabled APIs & services in the left sidebar. You should see Google Sheets API, Gmail API, and Google Drive API listed.

Don't see all three APIs?

Make sure you have the n8n Lead Rescue project selected in the project picker at the top. APIs are project-specific, so enabling them in a different project will not work.

If an API shows a Manage button instead of Enable, it is already enabled. That is fine.

Help me enable APIs in Google Cloud Console.

Configure the OAuth consent screen and create credentials

OAuth2 is a secure way for apps like n8n to access your Google account without knowing your password. Google requires you to configure a consent screen before you can create OAuth2 credentials.

In the left sidebar, click APIs & Services.
Click OAuth consent screen.
Select External as the user type, then click Create.
Enter n8n Lead Rescue in the App name field.
Enter your email address in the User support email field.
Scroll to the bottom and enter your email address again in the Developer contact information field.
Click Save and Continue.
On the Scopes page, click Save and Continue without adding any scopes.

You should now be on the Test users page. This is where you add yourself so you can complete the OAuth2 sign-in flow.

Click Add Users.
Enter your Gmail email address, then click Add.
Click Save and Continue.
On the Summary page, click Back to Dashboard.

Why External user type?

External means anyone with a Google account could use this app. Since the consent screen starts in testing mode, only the test users you manually added can complete the sign-in flow.

The Internal option is only available to Google Workspace (business) accounts. For personal Gmail accounts, External is the correct choice.

Now create the OAuth client credentials that n8n will use to authenticate.

In the left sidebar, click Credentials (under APIs & Services).
Click + Create Credentials at the top, then select OAuth client ID.
For Application type, select Web application.
In the Name field, enter n8n Lead Rescue.
Leave Authorized redirect URIs empty for now. You will add it from n8n in the next step.
Click Create.

A dialog titled OAuth client created appears showing your Client ID and Client Secret. Keep this dialog open or copy both values somewhere safe. You will need them in a moment.

Keep your credentials handy

If you accidentally close the dialog, you can find your Client ID and Client Secret again by clicking the OAuth client name under OAuth 2.0 Client IDs on the Credentials page.

Now switch to n8n to connect the Google Sheets credential.

Switch back to your n8n instance in your browser.
Click Credentials in the left sidebar.
Click Add Credential.
Search for Google Sheets OAuth2 API and select it.
You will see an OAuth Redirect URL field near the top of the credential form. Copy this URL. For a local self-hosted instance, it looks like http://localhost:5678/rest/oauth2-credential/callback.
Switch back to Google Cloud Console. Click the name of your OAuth client under OAuth 2.0 Client IDs.
In the Authorized redirect URIs section, click Add URI.
Paste the OAuth Redirect URL you copied from n8n, then click Save.

Now finish connecting the credential in n8n.

Switch back to n8n.
Paste your Client ID from Google Cloud Console into the Client ID field.
Paste your Client Secret into the Client Secret field.

Before you click the sign-in button, what do you think will happen? Will n8n connect to your Google account, or will you see an error?

Click Sign in with Google.
A Google sign-in window opens. Select your Google account.
You may see a warning that says the app is not verified. Click Continue (this is expected because your consent screen is in testing mode).
Grant the requested permissions and complete the flow.

Back in n8n, the credential should now show as connected. Click Save.

Sign-in failing or showing an error?

If you see a redirect URI mismatch error, make sure the OAuth Redirect URL you pasted into Google Cloud Console matches the one shown in n8n exactly. Check for trailing slashes or typos.

If you see an "access denied" error, confirm you added your Gmail address as a test user on the OAuth consent screen. The consent screen is in testing mode, so only manually added test users can sign in.

Help me fix my Google OAuth sign-in in n8n.

Now create the Gmail credential using the same Client ID and Client Secret.

In n8n, click Credentials in the left sidebar.
Click Add Credential.
Search for Google Mail OAuth2 API and select it.
Paste the same Client ID and Client Secret from your Google Cloud project.
Click Sign in with Google and complete the authorization flow again.
The credential should show as connected. Click Save.

Why use the same Client ID for both?

Both Google Sheets and Gmail credentials use the same OAuth2 flow. Since they share the same Google Cloud project, you can reuse the same Client ID and Client Secret. The OAuth Redirect URL is also the same for both, so no additional redirect URIs are needed.

You should now see two connected credentials in your n8n Credentials list: one for Google Sheets OAuth2 and one for Google Mail OAuth2.

Prepare your lead tracking spreadsheet

Every lead that submits the contact form will be logged as a row in a Google Sheets spreadsheet. You need to create this spreadsheet now and set up the column headers that n8n will map data into.

Open Google Sheets in a new browser tab.
Click Blank spreadsheet to create a new one.
Click the title in the top left (it defaults to "Untitled spreadsheet") and rename it to Lead Tracker.
In cell A1, type Name.
In cell B1, type Email.
In cell C1, type Phone.
In cell D1, type Message.
In cell E1, type Submitted At.

Your spreadsheet should now have five column headers in Row 1: Name, Email, Phone, Message, and Submitted At. The rest of the sheet is empty.

Copy the spreadsheet URL

Copy the URL from your browser's address bar and keep it somewhere handy. You will paste it into n8n in the next step when you connect the Google Sheets node to this spreadsheet.

Spreadsheet not saving?

Google Sheets saves automatically. If you see a "Saving..." message that does not go away, check your internet connection. The spreadsheet must be accessible from the same Google account you used for the OAuth2 credentials.

Help me set up my Lead Tracker spreadsheet.

Your Google Cloud credentials are ready and your Lead Tracker spreadsheet is waiting for data. Next up, you will build the form that captures leads and logs them straight into that spreadsheet.

Build the Lead Capture Form and Log to Sheets

Your Google Cloud credentials are set up and connected to n8n. Now it's time to create the entry point where leads actually reach you.

A contact form is the entry point for every lead. Without it, there is nothing to automate.

In this step, you'll build a form using n8n's Form Trigger node and wire it to Google Sheets. Every submission will automatically land as a new row in your Lead Tracker spreadsheet.

In this step, get ready to:

Create a new workflow with an n8n Form Trigger that captures name, email, phone, and message.
Connect a Google Sheets node that logs each submission to your Lead Tracker spreadsheet.
Test the full form-to-sheet pipeline by submitting test data and verifying it appears in your spreadsheet.

Create a new workflow with the Form Trigger

n8n's Form Trigger node generates a web form page and captures everything a visitor submits. It becomes the first node in your workflow, firing each time someone fills out the form.

Switch back to your n8n instance in the browser.
Create a new workflow.
Name the workflow Lead Rescue Machine.
Click Add first step on the canvas.
Search for n8n Form Trigger and select it to add it to your workflow.

What is the Form Trigger?

The Form Trigger is a built-in n8n node that generates a web form page for you. When someone submits the form, the trigger fires and passes the submitted data into your workflow. No external form tools needed.

In the Form Trigger settings, set Form Path to contact.

Why set a Form Path?

By default, n8n generates a long random ID in the form URL. Setting the Form Path to contact gives you a clean, memorable URL instead.

Now add the four fields that your form will collect. Each field is a form element.

Click Add Form Element.
Set Field Label to Name and Element Type to Text.
Turn on the Required Field toggle.
Add a second form element with Field Label set to Email and Element Type set to Email. Turn on Required Field.
Add a third form element with Field Label set to Phone and Element Type set to Text. Leave Required Field off.
Add a fourth form element with Field Label set to Message and Element Type set to Textarea. Turn on Required Field.
Set Respond When to Workflow Finishes.

Why set Respond When to Workflow Finishes?

This tells n8n to wait until the entire workflow has finished running before showing the visitor a confirmation. If something goes wrong mid-workflow, the visitor sees an error message instead of a false success.

Your Form Trigger node is now configured on the canvas. At the top of the node panel, you can see a Test URL and a Production URL. You'll use the Test URL shortly.

Add the Google Sheets node to log submissions

Now that the form captures lead data, you need somewhere to store it. The Google Sheets node writes each submission as a new row in your spreadsheet.

Close the Form Trigger settings panel.
Click the + connector on the Form Trigger node's output to add a new node.
Search for Google Sheets and select it.
Set Credential to connect with to the Google Sheets OAuth2 credential you created in Step 1.
Set Resource to Sheet Within Document.
Set Operation to Append Row.
Set Document to your Lead Tracker spreadsheet. Select By URL and paste the spreadsheet URL you noted in Step 1.

After selecting your spreadsheet, n8n auto-detects the column headers from Row 1. You should see mapping fields for Name, Email, Phone, Message, and Submitted At appear in the node settings.

Don't see your column headers?

Make sure your Lead Tracker spreadsheet has headers in Row 1: Name, Email, Phone, Message, Submitted At. Double-check that you pasted the correct spreadsheet URL and that your Google Sheets credential still shows as connected.

Try re-selecting the sheet in the node settings to force n8n to refresh the detected columns.

Help me troubleshoot why n8n isn't detecting my Google Sheets columns.

Now map each column to the corresponding form field so n8n knows which data goes where.

Map the Name column to the Form Trigger's Name field.
Map the Email column to the Form Trigger's Email field.
Map the Phone column to the Form Trigger's Phone field.
Map the Message column to the Form Trigger's Message field.
For the Submitted At column, switch the field to expression mode and enter the following expression:

{{ $now.format('yyyy-MM-dd HH:mm') }}

What does this expression do?

$now is an n8n variable that returns the current date and time. The .format('yyyy-MM-dd HH:mm') part formats it as a readable timestamp like 2026-08-15 09:30. This way, every submission gets an automatic record of when it arrived.

Test the form-to-sheet pipeline

Both nodes are wired up. Time to run the workflow and see if a form submission actually lands in your spreadsheet.

Click Execute Workflow in n8n.

n8n opens the test form in a new browser tab. You should see a styled form with all four fields you configured.

Enter Jane Smith in the Name field.
Enter jane@example.com in the Email field.
Enter 555-0123 in the Phone field.
Enter I would like to learn more about your services in the Message field.
Click Submit.

Before you check your spreadsheet, what do you think you'll find in the Lead Tracker?

Switch to your Lead Tracker spreadsheet in Google Sheets.

A new row appears in Row 2 with all five columns filled in. The Name, Email, Phone, and Message columns match what you typed. The Submitted At column shows an auto-generated timestamp.

Don't see a new row?

Make sure you clicked Execute Workflow before submitting the form. The test form only works when n8n is actively listening for submissions.

Check that the column headers in Row 1 of your spreadsheet match exactly: Name, Email, Phone, Message, Submitted At. Column name mismatches prevent the mapping from working.

Help me figure out why my form submission is not appearing in Google Sheets.

Your lead capture pipeline is working. Next up, you'll add instant Gmail notifications so the business owner knows the moment a new lead arrives.

Add Instant Owner Notification via Gmail

In Step 2, you connected your form to Google Sheets. Every submission now gets logged as a new row in your Lead Tracker spreadsheet.

A row in a spreadsheet is useless if nobody checks it. The business owner needs to know the instant a lead arrives so they can respond while the lead is still warm. In this step, you'll wire up a Gmail node that fires off an email notification the moment someone submits the form.

In this step, get ready to:

Add a Gmail node to the workflow and connect it to the Google Sheets node.
Configure the Gmail node to email the business owner with lead details.
Test the full form-to-Sheets-to-notification pipeline.

Add the Gmail node to your workflow

Your workflow currently ends at the Google Sheets node. You need a new node after it that sends an email every time a row is appended.

Return to your Lead Rescue Machine workflow in n8n.
Click the + button on the right side of the Google Sheets node to add a new connected node.
Search for Gmail and select it.

The Gmail node appears on your canvas, connected to the Google Sheets node output.

Click on the Gmail node to open its settings panel.
Set Credential to connect with to the Google Mail OAuth2 credential you set up in Step 1.
Set Resource to Message.
Set Operation to Send.
In the To field, enter your own email address (this is the business owner's inbox).

What did you just configure?

You told n8n which Google account to send from (your OAuth2 credential), what action to perform (send a message), and who receives it (your own email, acting as the business owner).

Every time the Google Sheets node finishes appending a row, this Gmail node fires next in the pipeline.

Set the subject line and email body

The notification needs to include the lead's name in the subject line and their full details in the body. You'll use n8n expressions to pull data from the Form Trigger node.

Click on the Subject field in the Gmail node settings.
Switch the field to Expression mode by selecting the Expression tab above the field (the field background turns purple).
Paste the following expression:

New Lead: {{ $('n8n Form Trigger').item.json['Name'] }}

What does this expression do?

The {{ }} brackets tell n8n to evaluate a dynamic value instead of using plain text. $('n8n Form Trigger') reaches back to the Form Trigger node's output and grabs the Name field the lead typed in.

The result is a subject line like "New Lead: Jane Smith" that tells the business owner exactly who submitted the form.

Set Email Type to HTML.
Click on the Message field and switch it to Expression mode.
Paste this HTML notification template:

<h2>New Lead Received</h2>
<p><strong>Name:</strong> {{ $('n8n Form Trigger').item.json['Name'] }}</p>
<p><strong>Email:</strong> {{ $('n8n Form Trigger').item.json['Email'] }}</p>
<p><strong>Phone:</strong> {{ $('n8n Form Trigger').item.json['Phone'] }}</p>
<p><strong>Message:</strong></p>
<p>{{ $('n8n Form Trigger').item.json['Message'] }}</p>

What does this HTML do?

Each <p> tag creates a separate line in the email. The <strong> tags bold the field labels so the business owner can scan the lead's details at a glance.

Every expression pulls directly from the Form Trigger output, so the email always contains the exact data the lead typed into the form.

Test the full notification pipeline

Your Gmail node is configured. Before you test, think about what you expect to happen when you submit the form. Will you see one thing happen, or two?

Click Execute Workflow in the top right of the n8n canvas.
n8n opens the test form in a new browser tab. Fill in sample lead data and click Submit.

Two things should happen within seconds. Switch back to your Lead Tracker spreadsheet. A new row with your sample data appears at the bottom.

Open your Gmail inbox.

You should see a new email with the subject line "New Lead:" followed by the name you entered. Open it and confirm it contains the lead's name, email, phone, and message.

Don't see the email in your inbox?

Check your Spam folder. Gmail sometimes flags automated emails from new senders.
Return to the n8n canvas and check the Gmail node for a red error indicator. Click the node to see the error details.
Make sure you selected the Google Mail OAuth2 credential, not the Google Sheets credential. They are separate entries even though they use the same Google Cloud project.
Confirm the To field contains a valid email address with no trailing spaces.

Still stuck? Why isn't my Gmail node sending the notification email in n8n?

Your workflow now logs every lead and pings the business owner instantly. But what happens when the owner is too busy to respond? In the next step, you'll add a timed follow-up email that keeps the lead warm automatically.

Add the Timed Follow-Up Email

Your workflow now logs every lead and pings the business owner instantly. But what happens when the owner is in a meeting, on a call, or simply away from their inbox?

The lead waits, gets impatient, and contacts a competitor. A timed follow-up email sent automatically to the lead buys time and shows the business is responsive, even when no human has acted yet. In this step, you will use the Wait node to pause the workflow and then fire a follow-up email to the lead after a configurable delay.

In this step, get ready to:

Add a Wait node that pauses the workflow for a timed interval.
Connect a second Gmail node that sends a follow-up email to the lead.
Publish the workflow and test the full end-to-end automation.

Add a Wait node for the delay

Right now, the Google Sheets node feeds directly into the Gmail notification node. You need a second branch from the Sheets node that runs in parallel: one branch notifies the owner, the other waits and then follows up with the lead.

On the workflow canvas, hover over the Google Sheets node and select the grey dot (or the Add node connector) on its right side.
Drag the arrow down and release it on an empty area of the canvas below the existing Gmail notification node.
In the node search panel that appears, search for Wait and select it.
n8n adds the Wait node to the canvas and opens its configuration panel.
Set Resume to After Time Interval.
Set Wait Amount to 1.
Set Wait Unit to Minutes.
Close the Wait node to return to the canvas.

You should now see two branches coming out of the Google Sheets node: one going to the Gmail notification node (top), and one going to the Wait node (below it).

What does the Wait node do?

The Wait node pauses the workflow for a set time before continuing to the next node. It offloads the execution data to the database and resumes automatically when the timer expires.

You are using 1 minute for testing. In production, you would change this to hours or days to give the business owner time to respond before the automated follow-up fires.

Why two branches instead of one chain?

If the Wait node sat between the Sheets node and the Gmail notification, the owner would have to wait 1 minute (or longer in production) before getting alerted. Parallel branches let the owner notification fire instantly while the follow-up email waits independently.

Add a Gmail node for the follow-up email

On the canvas, select the Add node connector on the right side of the Wait node.
Search for Gmail and select it.
Set Credential to connect with to the Google Mail OAuth2 credential you created earlier.
Set Resource to Message.
Set Operation to Send.

Now set the recipient to the lead's email address using an expression. This pulls the email the lead typed into the form.

Click the To field. Switch it to Expression mode (click the toggle or the expression editor icon next to the field).
Paste the following expression:

{{ $('n8n Form Trigger').item.json['Email'] }}

What does this expression do?

This reaches back to the Form Trigger node and grabs the Email field that the lead entered. The follow-up email goes directly to the person who submitted the form, not to the business owner.

Set Subject to:

Thanks for reaching out! Here's what happens next

Set Email Type to HTML.
In the Message field, switch to Expression mode and paste the following HTML:

<p>Hi {{ $('n8n Form Trigger').item.json['Name'] }},</p>
<p>Thank you for reaching out to us! We received your message and wanted to let you know that our team is reviewing it.</p>
<p>Someone will be in touch with you shortly. In the meantime, feel free to reply to this email if you have any additional details to share.</p>
<p>Best regards,<br>The Acme Solutions Team</p>

What does this email do?

This is the automated follow-up that fires after the Wait node timer expires. It addresses the lead by name using the Form Trigger expression, thanks them, and reassures them that someone will follow up. Even if the business owner has not responded yet, the lead feels acknowledged.

Scroll down to Send options (you may need to click Add option or expand the section).
Set Sender Name to Acme Solutions.
Close the Gmail node to return to the canvas.

Sender Name vs email address

The Sender Name controls the display name recipients see in their inbox (e.g., "Acme Solutions" instead of your raw email address). It does not change the actual sending address.

Publish and test the full workflow

Your workflow now has all three pieces: logging, instant notification, and a timed follow-up. Before it can process real form submissions automatically, you need to publish it.

Save the workflow by pressing Cmd+S (macOS) or Ctrl+S (Windows).
In the top-right corner of the editor, click the Publish toggle to activate the workflow.

Why do I need to publish?

Workflows that start with a trigger node must be published to run automatically. When a workflow is not published, you can only run it manually. Publishing makes the Production URL active so real form submissions are processed 24/7.

Open the n8n Form Trigger node by double-clicking it on the canvas.
Copy the Production URL (not the Test URL).
Open a new browser tab and paste the Production URL.

Test URL vs Production URL

The Test URL only works when you click Execute Workflow in the editor. The Production URL works at any time as long as the workflow is published. For this final test, use the Production URL to simulate a real submission.

Before you submit the form, think about this: what do you expect to happen after you click submit? How many emails should arrive, and when?

Fill in the form with sample lead data and submit it.

The form will take about 1 minute to respond

Because Respond When is set to Workflow Finishes, the form waits for the entire workflow to complete before showing the confirmation page. Since the Wait node pauses for 1 minute, the form will appear to load for about 1 minute. This is expected during testing.

Now confirm all three pieces fired correctly:

Open your Lead Tracker spreadsheet in Google Sheets. A new row should appear with the data you just submitted.
Check your Gmail inbox (the business owner's email). You should see a notification email with the subject line New Lead: followed by the lead's name.
After 1 minute, check the lead's email inbox. You should see the follow-up email with the subject Thanks for reaching out! Here's what happens next.

Return to n8n and click Executions in the left sidebar to open the Executions tab.
Find the most recent execution and click to open it.

You should see the execution log showing the workflow paused at the Wait node and then resumed to send the follow-up email. Both branches from the Google Sheets node executed successfully.

Follow-up email not arriving?

Make sure the Wait node is connected to the Google Sheets node output, not to the Gmail notification node.
Verify the To field in the follow-up Gmail node uses the expression {{ $('n8n Form Trigger').item.json['Email'] }}, not your own email address.
Confirm the workflow is published (the toggle in the top-right should be active).
Check your spam or junk folder.
Open the Executions tab to see if the execution errored at any node.
Help me debug why my follow-up email is not arriving after the Wait node.

Your lead-rescue automation is fully operational. Every form submission gets logged, the owner gets notified instantly, and the lead receives an automatic follow-up. In the Secret Mission, you will take it further by adding smart routing that treats urgent leads differently from general inquiries.

Secret mission

Add Smart Routing with IF Branching

Right now every lead gets the same timed follow-up, whether they are casually browsing or ready to buy today. In this secret mission, you will add conditional logic that detects urgent inquiries and fires an immediate personalized response. General leads continue through the standard timed follow-up path.

Clean Up Your Resources

This project runs entirely on free-tier services and your local n8n instance, so there are no ongoing costs. Decide whether to keep your resources running, pause them to come back later, or delete them entirely.

Resources you used:

n8n workflow: Lead Rescue Machine.
n8n credentials: Google Sheets OAuth2 and Google Mail OAuth2.
Google Cloud project: n8n Lead Rescue (with Sheets API, Gmail API, and Drive API enabled).
Google Sheets spreadsheet: Lead Tracker.

Keep everything running

No action needed. Choose this if you are still actively building on this workflow or plan to demo it to a client.

Your n8n workflow stays published and processes form submissions automatically.
Google API usage for Sheets and Gmail is well within free-tier limits for small business use.
Your Google Cloud project incurs no charges.

Pause - I'll come back to this later

Unpublish the workflow to stop it from processing new submissions. All your configuration and credentials stay intact.

In n8n, open the Lead Rescue Machine workflow.
Click the dropdown arrow next to the Publish button in the canvas header and select Unpublish.
The workflow stops running automatically but preserves all nodes, connections, and credentials.
When you are ready to resume, open the workflow and click Publish again.

Delete - I don't want to use this again

Remove all project resources and start fresh. Follow each step below.

In n8n, go to the workflow list on the Overview page.
Open the three-dot menu on the Lead Rescue Machine workflow and select Delete. Confirm the deletion. This also removes the workflow's execution history.
In n8n, go to Credentials from the left menu.
Delete both the Google Sheets OAuth2 credential and the Google Mail OAuth2 credential.
In Google Cloud Console, go to the IAM & Admin section and open Settings.
Click Shut down. Enter the project ID for n8n Lead Rescue, then click Shut down anyway. The project enters a 30-day recovery window before permanent deletion.
Open Google Sheets and delete the Lead Tracker spreadsheet. Right-click it in Google Drive and select Move to trash.

That's a Wrap!

Nice work! You just built a complete lead-rescue automation using n8n. Every form submission now triggers instant logging, owner notification, and an automatic follow-up email.

What you learned:

Built a lead-capture form using n8n's Form Trigger node and connected it to Google Sheets via OAuth2, logging every submission as a new row automatically.
Wired up instant Gmail notifications so the business owner knows about every new lead within seconds of a form submission.
Used the Wait node to queue a timed follow-up email to the lead, ensuring no inquiry goes cold even when the owner is busy.
Secret Mission: Added IF branching to route urgent leads to an immediate personalized response, demonstrating the conditional logic that turns a basic automation into a premium one.

Ready to quiz yourself?