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

Memberships

N8nLab

4.5k members • Free

The AI SEO Society (Free)

457 members • Free

SW Automation

6.6k members • Free

AI Acquisition Live

1.8k members • Free

AI Automation Growth Hub

2.5k members • Free

AI Systems & Soda

2.8k members • Free

Ai Automation Vault

14.8k members • Free

AI Automation Agency Ninjas

19.2k members • Free

AI Automation Mastery

10.4k members • Free

3 contributions to AI Automation Society
AI Email Automation for multiple items
Hey there! I built the AI Email Automation workflow, presented by Nate in his YT video. (Json data attached) It works well for one single email coming in from the trigger node ✅ But as soon as the trigger sends multiple items at once (which is the case when the workflow is active and you have received multiple emails before the next time the workflow execution starts), the emails get drafted in the same thread (see screenshot of inbox attached: Received 3 new emails and drafts of them being created in only the thread of the most recent one). ❌ Reason for problem: In the "createDraft" tool, the ThreadID is set to {{ $('Set Content').item.json.threadID }}, calling up the threadID, which has been set as a string parameter in the "Set Content" node. With the expression {{ $('Set Content').item.json.threadID }} the "createDraft" tool picks up only one thread ID, which is the threadID of the first email of all email items running through the workflow, so probably only referring to the first slot of the threadID parameter in "Set Content" node. Solution 1: 💡 Accessing the individual threadID of each itemIndex in the "Set Content" node by using the expression: {{$items("Set Content")[$itemIndex].json.threadID}} in the "createDraft" tool. Problem Solution 1: The ThreadID in the "createDraft" tool is for all the emails still the same & all drafts get put into one thread. And sometimes a draft gets created in all the email threads, but then the draft content is the same for all drafts. ❌ Solution 2: 💡 Creating a "loop over items(Split in batches)" node, which should send the items individually through the workflow while keeping the expression {{ $('Set Content').item.json.threadID }}. Problem for Solution 2: Exactly the same problem as for solution 1: Sometimes a draft gets created for all the required threadIDs, but then the draft is the same, so only one single email is matching. Or multiple drafts get created in one email thread. ❌
1 like • Apr 27
I have a solution to this @Max Stoebe I have previously worked on a solution like this. The solution was manually creating a draft node. you can check it out in this loom I made for a client(timeline- 1.20) https://www.loom.com/share/0a55a094d56647e090271b4e93144e0b Hit me up if its something that can solve your issue
1 like • May 1
@Max Stoebe this sounds like you just described RAG agents. Can I get more context of what your goal is..
Rate my first Voice agent!
I've recently been trying to get better at n8n and integration and I built a static voice agent! feel free to check it out. You can also reach out for collaborations http://youtube.com/watch?v=lBorKTLeEpo
Welcome! Introduce yourself + share a career goal you have 🎉
Let's get to know each other! Comment below sharing where you are in the world, a career goal you have, and something you like to do for fun. 😊
3 likes • Jan 2
Hey Guys. I'm Roy from Kenya! I've been working on AI automations for a while now and I want to master n8n. lets freaking do this!!
1-3 of 3
@roy-kahuthu-2781
AI enthusiast turned entrepreneur

Active 12d ago
Joined Dec 31, 2024
Powered by