Using LangChain agents to diagnose and repair n8n workflow errors autonomously. I built this (and 8 other Langchain agents) to wow the hiring manager at Langchain in my interview with them this morning I run a lot of workflows in n8n. When one fails, a global error handler catches it and hands it to a LangGraph agent. The agent diagnoses the failure and drafts a fix with Anthropic, then passes that fix to a different model from OpenAI to review and approve before anything is written. That second step is the whole point, and the design is model agnostic. The proposer and the reviewer are just two seats, and you can drop any model into either one. Right now Claude drafts the fix and an OpenAI model approves it, so no single model marks its own homework. The fix only goes live after that independent, cross-vendor review. Then the agent applies it through the n8n API and re-runs the workflow to confirm it actually worked. In the demo I break a workflow on purpose and let the agent repair it end to end. It triaged the error, proposed the fix, got it approved, wrote it back, and the workflow ran clean. The whole thing cost under 6 cents, and every step is traceable in LangSmith. I triggered this run by hand so it was easy to follow, but the agent is set to run automatically the moment a new error lands. It is still in testing, and I am keeping it that way on purpose, but the autonomous loop is the point. That last part matters more than the fix. When agents act on their own inside your systems, you have to see exactly what they did. Observability is not a nice-to-have, it is the architecture. . #AIAgents #n8n #LangGraph #AIOps #Automation

Before a single Google automation works in n8n, your agent needs permission to talk to Google. This is the one-time setup that unlocks all of it. Do it once and you reuse the same credential across everything you build after. Here is the whole thing, start to finish: 1. Create a clean Google Cloud project just for your automations. 2. Enable the Google APIs your agents actually use: Gmail, Calendar, Docs, Sheets, Drive. 3. Configure the OAuth consent screen. 4. Create an OAuth client (web application) and add the redirect URI from your own n8n instance. 5. Copy your Client ID and Secret, and download the JSON. 6. Add the scopes for the services you want, then add yourself as a test user so the login actually works. 7. Connect it all as a reusable Google credential in n8n, and test it. The video walks through every step on screen, so follow along with your own console open in another tab. One habit to build early: never keep your Client ID and Secret in plain text. Download the JSON, store it somewhere encrypted, and remember you can spin up a fresh OAuth client any time. Losing a key is not a crisis. VaultWarden is a great opensource password manager and vault. Why this one is first: it is the prerequisite for the builds coming next, including the email assistant workflow. Get it set up once and every Google automation after this just works. Follow along: - Watch the video above. - n8n's full Documentation - Google Cloud Console - New here? Grab the free starter kit (local n8n in Docker) so you have a place to build: Work through it, then drop a comment telling us what you connected first. Stuck on a step? Post your operating system and where you got stuck and we will walk you through it. Welcome to The Agent Lab. Let's build.