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

Owned by Jay

Lead Gen Secrets

24.3k members • Free

Cold email training & lead generation systems. Automate cold outreach with AI to attract high-quality B2B leads and get clients on autopilot.

AI AUTOMATION INSIDERS

5.1k members • Free

Learn Claude Code, AI Agents, and N8N. Install the EXACT AI systems I use inside my $1mil/mo companies. Sell my systems as an AI Agency offer.

Jens AI Community

1.2k members • Free

Chase AI+

1.2k members • $99/month

Poppy AI Viral Content Academy

4.3k members • Free

Skool Add-ons

1k members • Free

Skoot | CRM for skool

695 members • $99/month

Viral Media Coverage by Otter

141 members • Free

Tech Snack | Vibe Coding & AI

19.8k members • Free

Remote Sales Secrets

718 members • Free

AI ATM MACHINE

2.7k members • Free

233 contributions to AI AUTOMATION INSIDERS
0 likes • 1d
Jonathan, isolate the node before touching the whole template. Run it with a hard-coded domain and selector. If that works, the issue is the expression feeding the node, not DKIM. Most failures I see are simple: the domain includes a protocol, the selector is blank, or the private key got flattened into one line. Fix those, publish the TXT record, then verify DNS before testing mail.
Your AI gets dumber the longer you talk to it
Quick tip: Claude Code can hold a million tokens of context. I almost never let it get close. I keep my sessions under 30 percent. I will tolerate 40. Very rarely 50. After that I compact or clear and start fresh. Here is why. The bigger the context gets, the more tokens every single command burns, and the worse the output gets. At 29 percent, every command drags that whole 29 percent along with it. You pay for all of it, every time. That is slower and dumber on every step. So a bloated session costs you twice: more money and worse work. When a session starts to fill, I do not push through it. I compact, keep the important stuff, and keep moving. Lean sessions think better.
1 like • 1d
@Aj Silvers@Sam Bylett Yup, ask Claude to set up the status line for you. Other option is /context
Lead Qualification System Issue
Hi, I built this workflow that qualifies leads in n8n (see screenshot). I can't load all leads at once because my server then just crashes (runs out of RAM) and in order to run it I have to separate the main spreadsheet into multiple sheets and load them in manually every time the previous one finishes. ChatGPT keeps on telling me that I am supposed to make it so that it takes leads from the spreadsheet in batches instead of all at once so it's not so heavy on RAM, but I can't seem to figure out how to do this. Is this even a thing? If so, how would I do it please? Do we have any resources on it? Thanks for your time, Jan
Lead Qualification System Issue
0 likes • 2d
Yes, 100% a thing. The move is to stop treating the sheet like one giant input and make n8n pull a small chunk, process it, mark those rows done, then come back for the next chunk. Start with 25-50 rows. In Google Sheets, turn off Return All, pull a page, run it through Loop Over Items, then write a processed flag or cursor back to the sheet. If the AI step is what melts the server, cap concurrency and add a short Wait between batches. Do not aggregate the whole list until the end. That's what nukes RAM.
The Fully Auto GHL build video is live
I gave it one prompt describing a $20K three month program. It interviewed me to fill in the gaps, wrote a plan, then built the three step qualification form, the funnel pages, a round robin application calendar, and a nurture workflow with conditions, tags, opportunity creation, iMessage follow up, and a disqualify branch. Then it opened the pages in Playwright, took screenshots, and fixed its own design issues before I ever looked at them. I never touched the GHL UI once. Watch the full build 👉 https://www.youtube.com/watch?v=GWGRxP-JLk4 GHL's public API gives outside software 36 tools. The internal one the app uses on itself gives you everything. That's what this runs on. Keith wired it into his agency sub accounts and now builds 29 step automation sequences in under 5 seconds. If you're already a premium member, grab it here. You need three things to connect it: your private integration token, your location ID, and your session refresh token. The GHL Token Grabber extension pulls that last one for you in two clicks. If you haven't upgraded yet, this is the one to upgrade for. Fully Auto GHL, Meta Ads Pro, and the AI cold email system all live behind the same door 👉 https://leadgenjay.com/aia Worth knowing before you decide. Because of the support load and how fast we're updating this one, there's a real chance it becomes its own separate product. Anyone already inside keeps access. Sign up after the cutoff and you won't be covered. It runs in Claude Code or Codex. Either works, I used Codex in the video because I like watching the sub agents run. Build something with it and post it here 👊
0 likes • 3d
Jason, I’d use a fresh subaccount first, not a totally separate agency account. The main risk is the system touching live assets you forgot about, so isolating the build inside a clean location solves most of it. Different top-level account only makes sense if the account itself has sensitive live client stuff you cannot risk interrupting at all. Start boring: duplicate location, no live calendars, no payments, no active client workflows, then inspect every form, tag, calendar, and branch before moving anything over.
0 likes • 2d
If you want maximum downside protection, use a separate test account for the first build. A new subaccount is fine for most builds, but it still sits under the same agency account, so it is not a true firewall. My rule: sandbox first, duplicate anything important, then move the finished pieces into the live subaccount once you understand exactly what changed.
I paid $300/mo for Grokbot. My FREE agent won.
Grokbot went ultra viral and I fell for it. HARD. Signed up for the $300 a month heavy plan just to try it. Had Claude Code zip up my entire knowledge base and every scheduled task Bob runs, dropped the folder in, and Grokbot built 12 sub agents on its own. Named them, wrote their descriptions, all of it. Then I paused Bob and let Grokbot run my business. Cold email, presentations, n8n builds, Reddit posts. It did the work WORSE. Bob lives on a Mac Mini in my office and costs me nothing to run. And he already delegates to sub agents through Kanban when a job actually needs it. I'm keeping the Grok subscription anyway. Not for Grokbot. There's something else in there that changed how I run Claude Code completely, and that's the real sauce in this one. It's at the end of the video. Also, they dropped it to the $100 plan. Don't be me. Watch it here: https://www.youtube.com/watch?v=v8xFG4RmsLU Anyone else tried Grokbot yet? Curious if you got a different result than me.
1-10 of 233
Jay Feldman
7
5,652 points to level up
@leadgenjay
Lead Gen Jay here - YouTube's leading expert in AI Automation and B2B lead generation. Founder of Otter PR (2x Inc 5000 Winner) and NextWave.io.

Active 3d ago
Joined Jun 24, 2025
Miami
Powered by