Safety & audit

Scraper limits apply to local sync. Blocklist and audit log are shared via your Neon database.

Application limits

How lnkr caps sync volume, batch size, and cloud processing. Tune scraper settings via environment variables (see GitHub Secrets or .env.local).

Daily SN scrape limit · Scrapes available

10 profile scrapes available today (0 / 10 used)

10 left

One sync run per day is usually enough. After sync completes, run the complete pipeline to turn new leads into today's batch.

Outreach mode: Draft-only — nothing is posted or connected automatically
Daily batch: Top 10 qualified leads per day with AI drafts
SN profile sync: 0 / 10 profiles used today (10 remaining)
Posts per profile: Up to 5 recent posts read for warming comments
Enrich & score (Vercel): Up to 10 leads per button click — click again if you have more pending leads
GitHub sync: ~10–30 min per run; weekday auto-sync at 11:00 UTC. Complete pipeline runs cloud steps on existing leads while sync finishes in the background
Company cap: Max 2 leads from the same company in one daily batch

Scraper tuning (daily scrape cap, delays) is configured via environment variables — see Settings → Safety. Scraping Sales Navigator may violate LinkedIn's Terms of Service; use conservative limits.

Scraper safety limits

Live usage against your configured scrape caps. Change limits via Vercel env vars, GitHub Actions Variables, or `.env.local`.

Daily scrape limit: 0 / 10
Profile delay: 4s–10s
Posts per profile: 5

Browser session

LinkedIn session cookies live in GitHub Secrets and are used by the sn-sync workflow. Re-export when sync fails with a login timeout.

Sync method: GitHub Actions
LinkedIn session: Cookies configured

Session setup (admin, one-time)

GitHub Actions uses exported LinkedIn cookies — not a browser on Vercel. Re-export monthly or when sync fails with a login timeout.

On your computer: vercel env pull .env.local
Sign in once: bun sn:sync --login
Export cookies to GitHub Secrets: bun sn:export-cookies | gh secret set LINKEDIN_SESSION_COOKIES --repo owner/lnkr
Set GITHUB_SYNC_SESSION_CONFIGURED=true on Vercel after cookies are stored.

Do-not-contact list

Blocked leads are skipped during sync. Add LinkedIn profile URLs or emails you never want to outreach.

No blocked contacts yet.

Activity audit log

Recent agent actions — scrapes, scores, content generation, safety stops, and outreach tracking.

sn syncSnListConfig6/16/2026, 9:40:57 PM
scraped 10
scrape updateLead6/16/2026, 9:40:48 PM
scrape updateLead6/16/2026, 9:40:34 PM
scrape updateLead6/16/2026, 9:40:20 PM
scrape updateLead6/16/2026, 9:40:06 PM
scrape updateLead6/16/2026, 9:39:56 PM
scrape updateLead6/16/2026, 9:39:45 PM
scrape updateLead6/16/2026, 9:39:37 PM
scrape updateLead6/16/2026, 9:39:24 PM
scrape updateLead6/16/2026, 9:39:13 PM
scrape updateLead6/16/2026, 9:39:02 PM
generate contentGeneratedContent6/15/2026, 6:54:10 PM
generate contentGeneratedContent6/15/2026, 6:53:40 PM
generate contentGeneratedContent6/15/2026, 6:53:18 PM
generate contentGeneratedContent6/15/2026, 6:52:52 PM
generate content errorLead6/15/2026, 6:52:31 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:52:14 PM
generate content errorLead6/15/2026, 6:51:53 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:51:36 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:51:14 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:50:56 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:50:40 PM
generate contentGeneratedContent6/15/2026, 6:50:19 PM
generate contentGeneratedContent6/15/2026, 6:49:59 PM
generate contentGeneratedContent6/15/2026, 6:49:38 PM
generate content errorLead6/15/2026, 6:49:00 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:48:43 PM
generate content errorLead6/15/2026, 6:47:58 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:46:42 PM
generate contentGeneratedContent6/15/2026, 6:46:20 PM
generate content errorLead6/15/2026, 6:45:56 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:45:29 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:45:04 PM
No object generated: response did not match schema.
generate content errorLead6/15/2026, 6:44:46 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:44:30 PM
generate content errorLead6/15/2026, 6:44:08 PM
No object generated: response did not match schema.
generate contentGeneratedContent6/15/2026, 6:43:52 PM
generate contentGeneratedContent6/15/2026, 6:43:34 PM
generate contentGeneratedContent6/15/2026, 6:43:11 PM
generate content errorLead6/15/2026, 6:42:51 PM
No object generated: response did not match schema.