sales-lobstr

What this skill does

# Lobstr.io Platform Help

Help the user with Lobstr.io platform questions — from configuring ready-made scrapers and running data collection jobs through scheduling automation, exporting results, managing credits, and API integration. Lobstr.io is a no-code web scraping and data collection platform based in Saint-Mandé, France. It offers 50+ ready-made scrapers, multi-threading, cookie-based account sync, scheduled automation, and a full API with Python SDK, CLI, and MCP Server.

## Step 1 — Gather context


If `references/learnings.md` exists, read it first for accumulated knowledge.

Ask the user:

1. **What area of Lobstr.io do you need help with?**
   - A) Ready-made scrapers — choosing and configuring a pre-built scraper (Google Maps, LinkedIn, Twitter, YouTube, etc.)
   - B) No-code web app — running scrapers, managing runs, viewing results in the UI
   - C) Cookie-based account sync — scraping behind login walls (LinkedIn, etc.) using the cookie picking add-on
   - D) Scheduled automation — setting up recurring scraping jobs with triggers
   - E) Data export — exporting results to Google Sheets, Amazon S3, or SFTP
   - F) Webhooks — configuring run status notifications (run.running, run.paused, run.done, run.error)
   - G) API / SDK / CLI — programmatic access, Python SDK, CLI, MCP Server
   - H) Make integration — connecting Lobstr to make.com automation workflows
   - I) Enterprise custom scrapers — tailored data collectors for specific use cases
   - J) Account / Billing / Credits — pricing tiers, credit usage, browsing limits
   - K) Safety management — browsing limit protection to avoid account bans
   - L) Something else — describe it

2. **What's your role?**
   - A) Sales / business development
   - B) Marketing / growth
   - C) Developer / engineer
   - D) Data analyst / researcher
   - E) Agency / freelancer
   - F) Other

3. **What are you trying to accomplish?** (describe your specific goal or question)

**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

## Step 2 — Route or answer directly

If the request maps to a specialized skill, route:
- General prospect list strategy / building target lists -> `/sales-prospect-list`
- Cross-platform datan enrichment strategy -> `/sales-enrich`
- Email deliverability / verification strategy -> `/sales-deliverability`
- Connecting Lobstr to CRM or other tools via middleware -> `/sales-integration`
- Outscraper-specific questions -> `/sales-outscraper`

Otherwise, answer directly from platform knowledge using the reference below.

## Step 3 — Lobstr.io platform reference

**Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

## Step 4 — Actionable guidance

Based on the user's specific question:

1. **Setting up a Google Maps lead scraping job**:
   1. Go to the Lobstr scraper catalog and select "Google Maps Leads"
   2. Configure the scraper parameters — search query (e.g., "dentists in Austin, TX"), result limits, and any filters
   3. Add tasks — each task is a search query or URL to scrape
   4. Start the run — Lobstr executes the scraper with multi-threading for speed
   5. Monitor run status in the web app or via webhook notifications
   6. Export results to Google Sheets, S3, or download as file
   7. Each unique result costs 1 credit — monitor your credit usage in the dashboard

2. **Scraping LinkedIn Sales Navigator with cookie sync**:
   1. Install the Lobstr cookie picking browser extension
   2. Log into LinkedIn normally in your browser
   3. Click the extension to sync your session cookies with Lobstr — your password is never shared
   4. Select the "LinkedIn Sales Navigator Leads" scraper in Lobstr
   5. Configure search parameters (title, industry, location, company size, etc.)
   6. Enable safety management — set browsing limits to avoid LinkedIn detecting excessive automated activity
   7. Start the run and monitor progress — results include name, title, company, location, and profile URL
   8. Be conservative with volume — stay within safe browsing limits to protect your LinkedIn account

3. **Setting up scheduled recurring scraping**:
   1. Requires a paid plan (scheduling not available on Free tier)
   2. Configure your squid with the desired scraper and parameters
   3. Add your tasks (URLs or search queries)
   4. In the scheduling settings, define frequency (daily, weekly, or custom interval) and trigger conditions
   5. Set up notifications — configure webhooks for `run.done` and `run.error` events, or enable Gmail alerts
   6. Optionally configure auto-export to Google Sheets or S3 so results are delivered automatically
   7. Monitor credit consumption — recurring jobs use credits each time they run

4. **Using the API to automate scraping programmatically**:
   1. Get your API key from the Lobstr dashboard
   2. Create a squid: `POST /v1/squids` with scraper configuration
   3. Add tasks: `POST /v1/tasks` with URLs or parameters to scrape
   4. Start a run: `POST /v1/runs` referencing the squid
   5. Poll run status: `GET /v1/runs/{id}` until status is `done`
   6. Retrieve results: `GET /v1/results` for the completed run
   7. Alternative to polling: configure a webhook via `POST /v1/delivery?squid={id}` to receive a POST notification when the run completes
   8. Mind rate limits: `/results` is limited to 2 requests/sec — implement backoff when fetching large result sets

5. **Exporting results to Google Sheets**:
   1. Connect your Google account in Lobstr's integration settings
   2. After a run completes, select "Export to Google Sheets" from the results view
   3. Choose an existing spreadsheet or create a new one
   4. Free plan exports are capped at 30 rows — upgrade to a paid plan for full exports
   5. For automated exports, combine scheduling with the Google Sheets integration so each recurring run auto-exports

## Gotchas

> *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*

1. **Free plan is very limited — 100 credits, 30 rows/export, no scheduling, no Premium scrapers, 7-day data retention.** The free tier is suitable only for testing. Any serious data collection requires a paid plan starting at €50/month. Credits do not roll over, and the 30-row export cap means you cannot download full result sets on the free plan.
2. **Credits are consumed per unique result and do not roll over month to month.** Each unique result costs 1 credit regardless of which scraper produced it. Unused credits expire at the end of each billing cycle. Plan your scraping volumes to match your credit allowance, and monitor usage to avoid running out mid-month.
3. **Cookie-based account sync requires careful safety management to avoid platform bans.** When scraping behind login walls (especially LinkedIn), always configure browsing limits in Lobstr's safety management settings. Excessive automated activity on your account can trigger detection and lead to restrictions or bans. Start with conservative limits and increase gradually.
4. **Webhook endpoints must respond within 30 seconds with a 2xx status code, or Lobstr will retry.** If your endpoint is slow or returns an error, Lobstr retries up to 3 times with a 15-minute delay between attempts. After 3 failed attempts, the delivery is abandoned. Process webhook payloads asynchronously — accept the request quickly and handle the data in a background job.
5. **The /results endpoint has a strict 2 requests/second rate lim