Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Memberships

AI n8n Automation Collective

1.7k members • Free

Brendan's AI Community

21.6k members • Free

🎙️ Voice AI Bootcamp

7.6k members • Free

AI Automation Society

202.6k members • Free

46 contributions to AI Automation Society
Microsoft Outlook credentials failure
Is anyone else having Outlook issues? Is this an n8n failure?
This error debugging workflow has saved me many hours
Sharing is caring. This is a very simple workflow that reports errors to you, AND tells you what to fix. It has saved me many hours trying to figure out what was wrong. It uses n8n itself to debug your workflows. It costs nothing, and will point you to the exact problem with your workflows. Simply replace your n8n key and your ‘send from’ email, and you’ll get immediate notification when a workflow fails, a detailed description, and suggestions of exactly how to fix it. After setup, just go to the “Settings” in each workflow and under errors, select this workflow. Whenever/if it fails, this workflow will be triggered. Here is an example of the email you receive, with a link directly to the execution that failed. Hello, there has been an error in a workflow. Please check below for details: Direct Link To Affected Execution: https://xxxxxxxxxxxxxxxxxxxxxxxxx Name Of Affected Node: Clean up email Type Of Affected Node: n8n-nodes-base.set Error Message: Node 'Get Call Data' hasn't been executed 🤖 AI Debugging Assistant Analysis: Root Cause Analysis: The error "Node 'Get Call Data' hasn't been executed" occurs because of a logical branching issue in the workflow. The Check for CallID (IF node) creates two distinct execution paths. True Path: If a callId exists, the workflow proceeds to the Get Call Data (HTTP Request) node to fetch additional information. False Path: If a callId does not exist, the workflow bypasses Get Call Data and connects directly to the failed node, Clean up email. The Clean up email (Set node) contains an expression for the phone field that explicitly tries to access data from the Get Call Data node: $('Get Call Data').item.json.customer.number. When the workflow takes the "False Path" (because there is no callId), the Get Call Data node is skipped. Consequently, when the Clean up email node tries to execute its phone expression, it fails because Get Call Data has no output data, leading to the reported error.
This error debugging workflow has saved me many hours
0 likes • 5d
@Kevin troy Lumandas Yes! Exactly. This really points you in the right direction so you don't have to spend time trying to figure out the error.
0 likes • 5d
@Martin Sabo Yes that makes sense. If you have a workflow running 3 times a minute and failing, that would also trigger the error workflow 3 times a minute. So over night that could be a lot of extra executions.
🚀New Video: Build ANYTHING with Gemini 3 Pro and n8n AI Agents
Gemini 3 Pro is here, and the benchmarks are seriously impressive. In this video, I break down what makes Google’s new chat model stand out, where it performs best, and where it still falls short. I also run real tests inside n8n so you can see exactly how it behaves in automations and AI agent workflows. If you want to learn how to connect Gemini 3 Pro to n8n, when to use it, and how it can upgrade the systems you build, this video will walk you through everything step by step.
3 likes • 14d
One of my biggest challenges is with a transient voice agent (built in VAPI) interpreting email addresses. I've currently written two subworkflows to compare the caller's name (ex. Nate Herk) with the initial spoken email (what the voice agent thinks the email was). Ms and Ns are often confused, so the voice agent may "hear" mherk@yahoo. My workflow compares that to the spoken name using Claude Sonnet 4 for the reasoning, and changes the email from "M" to "N" as the first name starts with N. This is, of course, not 100% perfect logic. Would using Gemini 3 Pro to analyze the call be more accurate to get the emails correct?
1 like • 11d
Hi @Ruben Ledesma Hudson here is my strategy to get the emails corrected. First of all, I learned that your agent can get into a lengthy back-and-forth with a caller trying to get the email right. The agent keeps asking for the email, then confirming it, and if it is wrong, they just go on and on. So I have instructed my agent to only ask for the email twice, then move on. Since my office follows up on these, they will call and confirm. But, to get the email corrected, I've implemented some logic for both the email account (name prior to the "@") and the domain name. First, I get the caller's name and the "spoken" email. So if the account is something like mhawks@yahoo.com, but the agent heard nhawks@yahoo.com, it looks at the caller's name and determines that since the caller's first name was Mark, it should be mhawks@yahoo.com. I use a HTTP request to Claude to do this. {{ [ {"role": "user", "content": `You are a Phonetic Email Repair Engine. Your goal is to reconstruct a valid email address from a noisy transcript. Context: - Spoken Input: "${$json.spokenEmail}" - Customer Name: "${$json.customerName}" Your Goal: Convert the spoken input into a standard email address format. Rules for Transcription: 1. SPELLING MODE RECONSTRUCTION: The user may have spelled the email (e.g., "j as in juliet o h n"). - "j dash o dash h dash n" -> "john" - "b as in boy" -> "b" - "m like mary" -> "m" 2. PHONETIC MAPPING: - "at" / "add" -> "@" - "dot" -> "." - "underscore" -> "_" 3. REASONING WITH NAME: - If the input is "cathy" but the customer name is "Kathy", AND the transcript is ambiguous, prefer the spelling that matches the name. - HOWEVER, if the user explicitly spelled it out ("C as in cat"), IGNORE the name "Kathy". 4. DOMAIN FIXES: - "g mail" -> "gmail.com" - "out look" -> "outlook.com" If the input contains the phrase 'I didn't catch that' or 'No transcript found', return { "confidence": "low", "reasoning": "Audio missing" } immediately.
🚀New Video: How to Use the NEW Nano Banana 2 in n8n (cheaper & no watermark)
What a crazy week in the AI space... In this video, I break down Google’s new NanoBanana Pro image model, and it is hands down the most detailed image generator I’ve used so far. I’ll show you how to plug it into n8n to level up your AI agents and automation workflows, and how to get it running cheaper than the official price with no watermarks. We’ll walk through text to image, image to image, and using multiple input images so you can test different prompts right away. The setup is simple, there’s no code needed, and you can follow along step by step as we build this workflow together.
3 likes • 14d
Very cool. Here's how I'm going to use it: I create regular content using Perplexity for my HeyGen avatars. I'm going to implement NB3 to generate related content to use as a background for HeyGen. For example, one of my Avatars is for my termite and pest control company. If the script is about scorpions, NB3 can generate an image of scorpions that will be inserted with the avatar to create really relevant content. This is how we create content on autopilot. How will you use it?
n8n and PandaDoc document processing
This has been a long-running project for me. I needed a better way to present proposals from my termite and pest control company. Termite reports are regulated by the state, and they are difficult to interpret. We needed a better way to present our findings, and reduce steps for clients to accept our repair proposals. This workflow takes our report created with a rudimentary program. Luckily, the report can be emailed directly from the software. My workflow checks a dedicated outlook email inbox for new email with an attached pdf. It parses the flat file using PDF.CO to extract various values, creates a cover letter to interpret the original findings into a client-friendly letter, takes the proposal items and builds a smart shopping cart giving clients the ability to check the repairs they want, and sends it for signature (like a Docusign). There is a lot going on here, and I know there were others building workflows with PandaDoc. It is not cheap, but I built what I wanted and it is saving my staff a lot of time. Hopefully this reduces barriers for the client so we get higher acceptance! #PDF.CO #Outlook365 #PandaDoc
n8n and PandaDoc document processing
1 like • 17d
@Kevin troy Lumandas Thanks!
1-10 of 46
Philippe Heller
5
281points to level up
@philippe-heller-2951
Small business owner implementing AI wherever possible

Active 4d ago
Joined Jun 9, 2025
92065
Powered by