Hey Daniela V. . The $4 per 1k is specifically for certain Apify Actors like the Google Maps Scraper — it’s their “pay per event” pricing model. Different Actors have different rates. And yes, it does apply to Lindy users! Lindy has a native Apify integration, so you connect your Apify account and any pay-per-event or pay-per-result Actor works. You just need Apify credits in your account (they give you $5/month free on the free tier). The only ones that DON’T work through Lindy are rental-priced Actors. I’ve personally used it for LinkedIn scraping through Apify. Want me to walk you through the setup?
Daniela V. ah yeah, that's the downside of the Google search route — snippets cut off titles and LinkedIn doesn't index every profile fully. What actually works better: Instead of searching LinkedIn via Google, search the company's own website for their team page. Most companies list leadership with full names and titles. Try this prompt:
Search for: "[company name] team" OR "[company name] leadership" OR "[company name] about us"
Find the page that lists employees. Extract names and titles.
If no team page exists, try: "[company name] staff site:linkedin.com"Company websites are way more reliable for this than trying to scrape LinkedIn through Google — no truncation, no indexing gaps, and titles are always complete. If the company doesn't have a team page, Apify's LinkedIn Company Employees scraper is the nuclear option — it actually navigates LinkedIn properly instead of relying on Google's index. You'd call it via HTTP request in Lindy with your Apify API key. Free tier gives you enough for small batches.
Hey Daniela V., 600 credits for 2 leads is high. Main things I'd look at: Merge your two loops into one. Right now each lead goes through LinkedIn Enrichment AND Phone Numbers as separate loops — that's two full AI processing cycles per lead. Combine them into a single loop that does both in one pass. That alone could cut credits roughly in half. Disable tools you're not using. Each enabled tool gets loaded into context on every loop iteration even if the AI never uses it. Only keep the ones each step actually calls. Trim your prompts. Whatever's in those loop prompts gets processed on every iteration for every lead. Keep them tight — move any background context into the agent's Context field instead. Should get you closer to 150-250 credits for 2 leads. Happy to look at the prompts if you want to share them.
Hey Daniel L., The issue isn't your setup — it's what that action actually returns. The "LinkedIn companies by URL" action pulls company-level data (industry, size, description, HQ location) — it doesn't extract individual employees. LinkedIn locks people data behind authentication and aggressively blocks scraping of the employees/people tab, so no LinkedIn scraping tool in Lindy will reliably pull employee names + titles from a company URL. Use web search via an agent step. Replace the LinkedIn scraper with an agent step that has Search the Internet enabled. Prompt it like:
Search for employees at [company name] on LinkedIn.
Find 5-10 people with their full names and job titles.
Search: "[company name] employees site:linkedin.com/in"
Return as a list: [Name — Title]
This works because Google indexes LinkedIn profiles publicly even though LinkedIn's own pages block scraping. You'll get people who list that company in their profile.Hey Lauren G.! I've run into this exact issue. The problem is that "Find File" throws an error when it doesn't find anything — it doesn't return a "no file found" result that your Condition can evaluate. The flow dies at the Find File step before it ever reaches the branch. Replace "Find File" with an agent step that has the Google Drive skill enabled. Have it search for the file and return a JSON response like {"found": true, "file": "..."} or {"found": false}. Agent steps don't error out on empty results — they always produce output. Then your Condition branches on the found value.
Pat S. consider optimizing your agent prompts. Longer and vague prompts w/out specific instructions can eat alot of your credits. Wouldn't mind to take a look and offer helpful insights.