Apollo People Scraper

Description

With Apollo, you get up to 10,000 email credits every month. But here’s the catch: exporting emails to a CSV is limited. On the free plan, you can only export up to 120 emails per year, and even on paid plans, you’re capped at between 3,000 to 12,000 emails annually.

That means even though you have access to 120,000 email credits a year (10,000 per month), you’re stuck with exporting just a fraction of that.

But here’s the good news! With this scraper, you can bypass those export limits and download up to 10,000 emails per month (or 120,000 per year) on any plan. You’ll also get all the details from your Apollo leads search, like emails, phone numbers, and more.

How Does It Work?

This tool works using your Apollo login credentials.

1. Login Details: Just input your login email and password in the corresponding fields.

2. Running the Scraper:

   • Search for leads on Apollo like you normally would.
   • Once you have your search results, copy the URL from the address bar and paste it into the scraper’s “Search URL” input.
   • You can also specify a list name. If a matching list isn’t found, the scraper will create one and save all your leads there.

3. Flexible Scraping Options:

   • You can scrape a specific range of pages by setting the Start Page and Count parameters.
   • Make sure to use a proxy from the same country as your Apollo login location.

Best Practices for Getting the Most Out of the Scraper

To ensure smooth operations and avoid issues:

• Set a longer delay between actions (5-60 seconds is ideal).
• Don’t scrape more than 1,000 records per day.
• Always use the same proxy country for each run, matching the location from which you typically log in.
• Avoid scraping with the same Apollo account simultaneously on different sessions.
• For best results, don’t use free email addresses (like Gmail, Yahoo, or Outlook) when creating Apollo accounts—they limit your email credits to just 125 per month.
• If the scraper stops before completing your request, check the logs to ensure you still have enough monthly email credits.

Sample Output Data

Integrations

You can use Make to integrate Apollo leads with any other SaaS platform by designing your own automation flows.

Apollo Data Fields Documentation

This document provides a description of the JSON data from Apollo.io. The data represents information about a person, including their contact details, employment history, and organizational details.

Person Information

• id: Unique identifier for the person.
• first_name: First name of the person.
• last_name: Last name of the person.
• name: Full name of the person (combination of first name and last name).
• linkedin_url: URL of the person's LinkedIn profile.
• title: Job title of the person.
• email_status: Status of the person's email verification (e.g., "verified").
• photo_url: URL of the person's photo.
• twitter_url: URL of the person's Twitter profile (null if not available).
• github_url: URL of the person's GitHub profile (null if not available).
• facebook_url: URL of the person's Facebook profile (null if not available).
• extrapolated_email_confidence: Confidence level of extrapolated email (null if not available).
• headline: A brief description of the person's job role or headline.
• email: Masked email address of the person for privacy protection.
• organization_id: Unique identifier of the organization the person is associated with.
• employment_history: Array of objects representing the person's employment history (see details below).
• state: State/region of the person.
• city: City of the person.
• country: Country of the person.

Employment History

Each object in the employment_history array represents a past or current job position of the person.

• _id: Unique identifier for the employment record.
• created_at: Date and time when the record was created.
• current: Boolean value indicating if the employment is the current job (true) or a past job (false).
• degree: Degree obtained by the person during this employment (null if not available).
• description: Description of the job role (null if not available).
• emails: Array of emails associated with the job role (null if not available).
• end_date: Date when the person left the job (null for current jobs).
• grade_level: Grade level of the person in the job (null if not available).
• kind: Type of employment (null if not available).
• major: Major subject studied during this employment (null if not available).
• organization_id: Unique identifier of the organization associated with this employment.
• organization_name: Name of the organization associated with this employment.
• raw_address: Raw address of the organization (null if not available).
• start_date: Date when the person started this job.
• title: Job title during this employment.
• updated_at: Date and time when the record was last updated.
• id: Unique identifier for the employment record (same as _id).
• key: Key identifier for the employment record (same as _id).

Organization Information

• organization: Object representing details of the organization the person is associated with (see details below).

Organization Details

• id: Unique identifier of the organization.
• name: Name of the organization.
• website_url: URL of the organization's website.
• blog_url: URL of the organization's blog (null if not available).
• angellist_url: URL of the organization's AngelList profile (null if not available).
• linkedin_url: URL of the organization's LinkedIn page.
• twitter_url: URL of the organization's Twitter profile.
• facebook_url: URL of the organization's Facebook page (null if not available).
• primary_phone: Object containing the primary phone number of the organization (see details below).
• languages: Array of languages spoken by the organization (empty array if not available).
• alexa_ranking: Alexa ranking of the organization's website (null if not available).
• phone: Primary phone number of the organization.
• linkedin_uid: LinkedIn UID of the organization.
• founded_year: Year when the organization was founded.
• publicly_traded_symbol: Symbol of the organization's publicly traded shares (null if not available).
• publicly_traded_exchange: Exchange where the organization's shares are publicly traded (null if not available).
• logo_url: URL of the organization's logo.
• crunchbase_url: URL of the organization's Crunchbase profile (null if not available).
• primary_domain: Primary domain of the organization's website.
• sanitized_phone: Sanitized version of the primary phone number.
• persona_counts: Object containing counts of different personas associated with the organization.

Phone Numbers

• phone_numbers: Array of objects representing phone numbers associated with the person (see details below).

Phone Number Details

• raw_number: Raw phone number (with country code) associated with the person.
• sanitized_number: Sanitized version of the phone number (without country code).
• type: Type of the phone number (e.g., "work_hq").
• position: Position of the phone number in the array.
• status: Status of the phone number (e.g., "no_status").
• dnc_status: DNC (Do Not Call) status of the phone number (null if not available).
• dnc_other_info: Additional information related to DNC status (null if not available).

Additional Information

• departments: Array of department names associated with the person.
• subdepartments: Array of subdepartment names associated with the person.
• functions: Array of function names associated with the person.
• seniority: Seniority level of the person's job role (e.g., "manager").
• contact_stage_id: Unique identifier of the contact stage.
• owner_id: Unique identifier of the owner of the person's contact information.
• creator_id: Unique identifier of the creator of the person's contact information.
• person_id: Unique identifier of the person (same as id).
• email_needs_tickling: Boolean value indicating if the person's email needs attention (e.g., for follow-up).
• source: Source from where the person's information was obtained (e.g., "search").
• original_source: Original source of the person's information (e.g., "search").
• present_raw_address: Current address of the person.
• linkedin_uid: LinkedIn UID of the person.
• salesforce_id: Salesforce ID associated with the person (null if not available).
• salesforce_lead_id: Salesforce lead ID associated with the person (null if not available).
• salesforce_contact_id: Salesforce contact ID associated with the person (null if not available).
• salesforce_account_id: Salesforce account ID associated with the person (null if not available).
• crm_owner_id: CRM owner ID associated with the person (null if not available).
• created_at: Date and time when the person's record was created.
• emailer_campaign_ids: Array of campaign IDs associated with the person's emailer.
• direct_dial_status: Status of the person's direct dialing option (null if not available).
• direct_dial_enrichment_failed_at: Date and time when direct dial enrichment failed (null if not available).
• email_source: Source of the person's email (e.g., "crm_csv").
• account_id: Unique identifier of the associated account.
• last_activity_date: Date of the person's last activity (null if not available).
• hubspot_vid: HubSpot VID associated with the person (null if not available).
• hubspot_company_id: HubSpot company ID associated with the person (null if not available).
• crm_id: CRM ID associated with the person (null if not available).
• sanitized_phone: Sanitized version of the person's phone number.
• merged_crm_ids: IDs of merged CRM records associated with the person (null if not available).
• updated_at: Date and time when the person's record was last updated.
• queued_for_crm_push: Date and time when the person's record was queued for CRM push (null if not available).
• suggested_from_rule_engine_config_id: Rule engine configuration ID for suggestions (null if not available).
• email_unsubscribed: Unsubscription status of the person's email (null if not available).
• label_ids: Array of label IDs associated with the person.
• has_pending_email_arcgate_request: Boolean value indicating if there are pending email arcgate requests for the person.
• has_email_arcgate_request: Boolean value indicating if there are email arcgate requests for the person.
• existence_level: Existence level of the person's contact information (e.g., "full").
• email_from_customer: Email received from the customer (null if not available).
• typed_custom_fields: Object containing custom fields associated with the person (empty if not available).
• email_true_status: True status of the person's email (e.g., "Verified").
• updated_email_true_status: Boolean value indicating if the true email status was updated.
• contact_rule_config_statuses: Array of contact rule