Block 1 - AI Agent
- Type / Role
- @n8n/n8n-nodes-langchain.agent - agent
- Config choices
- Version 2.2
This workflow is provided as-is. Please review and test before using in production.
Automatically Reply to Customer Emails with Airtable, Gmail, and OpenAI Introduction This guide walks you step by step throug...
@n8n/n8n-nodes-langchain.agent, n8n-nodes-base.gmailtrigger, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.airtable, n8n-nodes-base.gmail, @n8n/n8n-nodes-langchain.memorybufferwindow, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Baptiste Fort.
Original n8n.io sourceThis guide walks you step by step through setting up an automated agent that:
Before you start, you’ll need:
No need to build everything from scratch — here’s a ready-to-use base you can copy:
👉 Open the Airtable base
It already contains the following structure:
You can reuse it as it is or duplicate it into your Airtable account.
Alright, now that we have our Airtable base ready, we need to capture customer emails.
That’s the job of the Gmail Trigger. Basically, this node lies in wait inside your inbox, and as soon as a new message arrives… bam, your workflow fires up.
Every Minute.Message Received.Message Received.OFF).When you execute the node, you should see:
And that’s it — your Gmail Trigger is set up. In short, the moment a customer writes “Hey, I have an issue with my account,” your workflow kicks in instantly (well, almost — it checks every minute).
After configuring your Gmail Trigger (which captures incoming customer emails), you now need a brain to take over, analyze the email, and draft a reply.
That’s where the AI Agent node comes in.
The AI Agent node is used to:
In short, it’s your 24/7 support colleague, but coded as a bot.
Define below. When you run this node, you should see in the output:
output containing the automatically generated AI reply. 👉 With the Gmail Trigger you capture emails, and with the AI Agent you get a reply ready to send — as if you had written it yourself.
Now that your AI Agent generates replies, you need to store them somewhere to keep a clear record of all interactions.
That’s where Airtable comes in.
You’ve already copied my ready-to-use Airtable base:
👉 Access the base
This base contains a table Email Support Logs with the following columns:
Create. Then, link the fields as follows:
{{ $('Email Received').item.json.Subject }} {{ $('Email Received').item.json.From }} {{ $('Email Received').item.json.snippet }} {{ $('AI Agent').item.json.output }} {{ $now }}For each new email received:
👉 You now have a fully automated customer support log.
Now that you’re storing each interaction in Airtable, it’s time to send your AI’s reply directly back to the customer.
This closes the loop: customer writes → AI replies → everything gets logged in Airtable.
Reply. {{ $('Email Received').item.json.threadId }}{{ $('Email Received').item.json.From }}Re: {{ $('Email Received').item.json.Subject }}{{ $('AI Agent').item.json.output }}When a customer sends an email:
Your customer receives a quick, personalized, and natural reply without you typing a single word.
👉 You now have a complete support agent: listen, analyze, log, reply.
Want to save hours each week? Visit Agence automatisation 0vni.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automatically reply to customer emails with Airtable, Gmail, and GPT-4.1 Mini |
|---|---|
| Complexity | intermediate |
| Nodes | 12 |
| Categories | AI Chatbot |
| Author | Baptiste Fort |
| Published | 17 Sept 2025 |
Use the JSON export at /data/workflows/8676/8676.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Automatically Reply to Customer Emails with Airtable, Gmail, and OpenAI Introduction This guide walks you step by step throug...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your AI Chatbot use case.