ScraperCity + GoHighLevel

Before You Start: What You Need

• A ScraperCity account on any plan ($49/mo, $149/mo, or $649/mo). Your API key is at app.scrapercity.com/dashboard/api-docs.
• A GoHighLevel sub-account. The Contacts API requires a Location-level token - either a Private Integration Token scoped to the sub-account, or a location-level OAuth access token.
• Your GHL locationId - the unique ID for the sub-account where contacts will be created. Find it in Settings inside any sub-account.
• Any custom fields you want to populate (job title, LinkedIn URL, etc.) must already exist in GHL under Settings - Custom Fields before you push data to them.

Setup

curl -X GET "https://app.scrapercity.com/api/v1/database/leads?title=CEO&industry=real%20estate&country=United%20States&hasEmail=true&limit=50" \
  -H "Authorization: Bearer YOUR_SCRAPERCITY_KEY"

curl -X POST "https://app.scrapercity.com/api/v1/apollo/scrape" \
  -H "Authorization: Bearer YOUR_SCRAPERCITY_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "titles": ["CEO", "Founder"],
    "industries": ["Real Estate"],
    "locations": ["United States"],
    "limit": 100
  }'

curl -X POST "https://services.leadconnectorhq.com/contacts/" \
  -H "Authorization: Bearer YOUR_GHL_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Version: 2021-07-28" \
  -d '{
    "firstName": "Jane",
    "lastName": "Smith",
    "email": "[email protected]",
    "phone": "+15551234567",
    "companyName": "Acme Corp",
    "locationId": "YOUR_LOCATION_ID",
    "tags": ["scraped-apollo"],
    "customFields": [
      { "key": "job_title", "value": "CEO" },
      { "key": "linkedin_url", "value": "https://linkedin.com/in/janesmith" }
    ]
  }'

Automate with n8n, Zapier, or a Script

You do not need to write a custom server to run this pipeline. Three common approaches work well depending on your technical comfort level:

Option A - Node.js / Python script

The most flexible option. Pull leads from ScraperCity, loop through the results, and POST each one to GHL. Add a small delay between requests to stay under the GHL burst limit (100 requests per 10 seconds). Here is a minimal Node.js example:

const leads = await fetch('https://app.scrapercity.com/api/v1/database/leads?title=CFO&hasEmail=true&limit=100', {
  headers: { Authorization: 'Bearer YOUR_SCRAPERCITY_KEY' }
}).then(r => r.json());

for (const lead of leads.data) {
  await fetch('https://services.leadconnectorhq.com/contacts/', {
    method: 'POST',
    headers: {
      Authorization: 'Bearer YOUR_GHL_TOKEN',
      'Content-Type': 'application/json',
      Version: '2021-07-28'
    },
    body: JSON.stringify({
      firstName: lead.first_name,
      lastName: lead.last_name,
      email: lead.email,
      phone: lead.phone,
      companyName: lead.company_name,
      locationId: 'YOUR_LOCATION_ID',
      tags: ['scraped-database'],
      customFields: [
        { key: 'job_title', value: lead.title },
        { key: 'linkedin_url', value: lead.linkedin_url }
      ]
    })
  });
  // Pause 150ms between requests to stay under GHL burst limit
  await new Promise(r => setTimeout(r, 150));
}

Option B - n8n workflow

In n8n, use an HTTP Request node to call the ScraperCity endpoint. Connect it to a second HTTP Request node configured as a POST to https://services.leadconnectorhq.com/contacts/ with the GHL token in the Authorization header and Version: 2021-07-28 as a second header. Use the Split In Batches node between the two to pace requests and respect the GHL rate limit. You can schedule the workflow to run on a cron - every morning, every hour, or after a ScraperCity webhook fires.

Option C - Zapier

Zapier has a native GoHighLevel integration. Use a Webhook trigger (or a Schedule trigger) to kick off a Zap, call the ScraperCity API via a Zapier Webhooks step to pull leads, then use the GoHighLevel "Create/Update Contact" action to push each one. Zapier handles the auth handshake for GHL natively - you just connect your GHL account and map fields. This works well for low-to-medium volume (a few hundred leads per run) without writing any code.

Common Use Cases

Performance Tips

• Batch size: Pull up to 100 leads per ScraperCity Lead Database request (the per-page limit). Process each page and POST contacts before fetching the next page - this keeps memory usage low and makes errors easier to recover from.
• Rate pacing: Add a 150-200ms sleep between GHL POST requests. At that pace you will push roughly 400-500 contacts per minute, well within the 100 requests/10 seconds burst limit. For overnight batch runs, pace is not critical - focus on the daily 200,000 request ceiling if you are pushing very large volumes.
• Use the upsert endpoint: If you run regular updates (e.g. weekly lead refreshes), use POST /contacts/upsert so existing contacts get updated rather than duplicated. Match on email.
• Filter before you push: Run ScraperCity emails through the Email Validator endpoint ($0.0036/email) before creating GHL contacts. Invalid or catch-all emails waste GHL workflow sends. Validate first, push only verified or valid emails.
• Tag everything: Apply a source tag on every contact you create (e.g. "apollo-ceo-realestate" or "maps-plumbers-dallas"). This makes it easy to segment contacts in GHL, measure campaign performance per source, and clean up or exclude specific batches later.
• Apollo delivery timing: Apollo scrapes take 11-48+ hours. Set up a ScraperCity webhook so your script is notified when results are ready, rather than polling repeatedly. The webhook URL is configured at app.scrapercity.com/dashboard/webhooks.

FAQ