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

Memberships

Automatable Free

15.8k members • Free

Skool Growth Free Training Hub

8.3k members • Free

Skool Community (deutsch)

5.1k members • Free

AI AUTOMATION INSIDERS

4.3k members • Free

Dopamine Digital

6.9k members • Free

Lead Gen Insiders 🧲

1.8k members • $1,497

Lead Gen Secrets

23.5k members • Free

Content Creator Cashflow

3.2k members • Free

9 contributions to AI AUTOMATION INSIDERS
Email Verifier app — where do I get the Reacher (Cloudflare Access) credentials?
Hey everyone, I just set up the Email Verifier app locally. Everything's working so far, Supabase is connected, migrations ran, login + dashboard work, account has its 100 credits. The only thing left is the actual verification. When I try to verify an email I get: "Email verification service is currently unavailable. Please try again later." I traced it to the Reacher integration. The app needs these in .env.local: - REACHER_CF_CLIENT_ID - REACHER_CF_CLIENT_SECRET (Cloudflare Access headers for reacher.nextwave.io — the docs say "replace with actual credentials from Cloudflare Access".) Where do I find these credentials inside the membership? I checked the Installation Guide page but it only covers unzip → GitHub → Claude Code, nothing about the Reacher / API keys. While I'm at it — same question for the no2bounce key (NO2BOUNCE_API_KEY) for catch-all verification. For reference, my license file says: Thanks a lot! 🙏
1 like • 8d
Ahh great, thanks heaps Jordan!
What's your biggest bottleneck right now?
Drop it below. Curious what everyone's actually dealing with.
0 likes • 8d
Offer
A Calude skill to build Claude skills?
I’d like to turn my own frameworks into Claude Code skills, not just prompt templates, but skills that preserve the original reasoning structure, questioning flow, prioritization logic, and behavioral consistency. What’s the best process for doing this properly? A few questions for experienced builders: 1. How do you structure complex frameworks into reliable Claude skills? 2. Is it better to use one large orchestrator skill or multiple modular skills? 3. How do you preserve deep reasoning instead of getting generic AI responses? 4. Any proven patterns for coaching, questioning, or diagnostic frameworks? 5. How do you handle sequencing, memory, and trigger conditions? 6. Any good repos, starter kits, or “meta-skills” for building custom skills? 7. What are the biggest mistakes people make when designing Claude skills? Example: One of my frameworks requires the AI to first diagnose the user’s active identity pattern before asking solution-oriented questions. The order matters a lot. Would love to learn from people already building advanced Claude Code skills at scale. Thanks heaps in advance for your takes!
0 likes • 21d
@Zillion Wong Thank you for your extensive input. i will dig into it!
UPDATE: Shorts Idea Scraper V2 is LIVE
One of my favorite automations was long overdue for an overhaul and improvement. Please watch this video to learn about the patch for this must-have automation for content creators. The updated JSON is available in the Social Media module as well as the link to the Notion database to copy. For those not yet in the AI Automation Insiders Premium, NOW is your time. Get in here to access all my best templates, tools, and coaching. Thank you and enjoy!!!
UPDATE: Shorts Idea Scraper V2 is LIVE
0 likes • May 13
Is there acess to notion as mentioned in the video. I could not find it linked anywere. Thanks!
😩 I kept losing deals... so I built an AI to fix that problem.
Have you resold anything you've built yet for 10K or more? I built this to solve my own problem, but now I have prospect that want it built and customized for their offers. The leads were showing up to calls. The offer was valuable. The pipeline was pumping. And I kept losing deals I knew I should have closed. You are doing the work. Jay's system is working. The meetings are booking. And then you get on the call. And somewhere between the intro and the close, something leaks. You can feel the moment it happens. The energy shifts. The prospect gets vague. You push a little. It goes sideways. There is a specific kind of embarrassment in getting off a call knowing you had them and lost them. For months I told myself the lead was not quite right. Or the offer needed tweaking. Or the prospect was not serious. The harder thing to say out loud: The money was not walking away because of the lead, the offer, or the pipeline. It was walking away because of what I was doing on the call. This is what I could not see at the time: The problem was not my script. It was not my objection handling. It was not my closing questions. The problem was that I walked into every call needing the close. The prospect could feel it before I opened my mouth. Every call where I needed them to say yes was a call that ended with them saying maybe. February 2025: $300 per booked call. Nothing I was proud of. February 2026: $1,300 per booked call. 30 percent close rate. $81,400 that month. $558K on the year. Same ICP. Same cold email system. Same pipeline. The only thing that changed was my skills, and 1000 call reps. Here is what most people in this community are sitting on right now: The gap between getting the meeting and closing it is where most of the money in your business lives. Not in more volume. Not in a better offer. In what happens on the call. I lived in that gap for a long time. What moved things for me was not a script or a tactic. It was getting into a real coaching structure.
😩 I kept losing deals... so I built an AI to fix that problem.
0 likes • May 13
REFLEKT
1-9 of 9
Peter Litke
2
11points to level up
@peter-litke-5015
Kundengewinnung

Online now
Joined Feb 20, 2026
Powered by