This is exciting! I really want to help as many people as I can make $1,000,000 (or more!)! If I can help or create or share anything that will help you let me know! Comment with your goals and your skills and I can try my best! Happy Friday!!

Hi, really need reccommendations which AI tools can one use for marketing. Would really appreciate your help. Thanks

Huge shoutout to the Top 5 Members of AI Automation Society for July! These are the people leading the way, sharing knowledge, and helping spread the AIS culture: 1️⃣ @Titus Blair – Absolutely crushing it this month! 💪 2️⃣ @Michael Wacht 3️⃣ @Yash Chauhan 4️⃣ @Ilya Emeliyanov 5️⃣ @Shashee Dean And a special mention to @Rodrigo Santos, who landed in 6th place and just missed the Top 5. We’re rooting for you to break through next month! 👏 Keep contributing, sharing wins, and helping others grow! Our community gets better because of you. Let’s keep building, keep learning, and keep spreading that AIS energy. 🚀 Cheers, Nate

Can someone pls help me with the configuration settings with sub workflows.

Hi, I'm building a driver matching workflow and I'm stuck on a data scoping issue inside a loop. The Goal:Inside a Loop Over Items node that processes a list of drivers, I need to use the Airtable - Create Record node to create an entry in an "Interest Log" table. This new log entry needs to link to two different records: 1. The Booking Request (data from a node before the loop started). 2. The Current Driver (data from the current iteration of the loop). The Problem:My Airtable - Create Record node is failing to create the two separate links correctly. When the record is created in Airtable, both the Linked Request ID and Linked Driver ID fields end up pointing to the same incorrect Record ID (the ID of the new Interest Log entry itself). My Setup: - Before the loop, a Set node creates a combined data object for each driver: { "driverRecord": {...}, "requestRecord": {...} }. - The Loop Over Items iterates through this. - Inside the loop, the Airtable - Create Record node uses these expressions for the linked fields: Even though the expressions {{$json.requestRecord.id}} and {{$json.driverRecord.id}} show the correct, distinct IDs in the n8n editor's preview, the links created in Airtable are wrong. My Question:What is the most reliable n8n pattern or expression syntax to use inside a loop to correctly populate two different "Link to another record" fields in an Airtable Create Record operation, where one ID comes from the loop's current item and the other ID comes from data that was passed into the loop?