Skip to main content

Apollo Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an Apollo location.
apollo_api.png

Apollo

Create an Apollo Destination​

  1. Click the + icon on the Nexset that will be sent to the Apollo destination, and select the Send to Destination option from the menu.

  2. Select the Apollo connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Apollo account, and click Next; or, create a new Apollo credential for use in this flow.

  3. In Nexla, Apollo destinations can be created using pre-built endpoint templates, which expedite destination setup for common Apollo endpoints. Each template is designed specifically for the corresponding Apollo endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Apollo destinations can also be configured manually, allowing you to send data to Apollo endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Apollo endpoints. Each template is designed specifically for the corresponding Apollo endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Enrich Person

    This endpoint calls Apollo's POST /api/v1/people/match endpoint to enrich a single person's profile with Apollo's contact, employment, and firmographic data. Use it to enrich inbound leads, MQLs, or contact records using a known identifier such as email, LinkedIn URL, or first/last name + company.

    • Each upstream record must include at least one identifier that Apollo can match against — typically an email, a linkedin_url, or a combination of first_name, last_name, and one of organization_name, domain, or id.
    • The full upstream record is sent as the JSON body of the POST /people/match request. Use the Nexla transform layer to shape upstream attributes into the field names that Apollo's match endpoint expects.
    • Optional reveal flags (reveal_personal_emails, reveal_phone_number) can be included in the record body to request work or personal email and phone enrichment. Each reveal consumes additional Apollo credits.

    Person enrichment consumes Apollo credits according to your account's pricing plan. The credit cost depends on which reveal flags are enabled and which data sources successfully return enrichment. For full details, see the Apollo People Enrichment documentation.

    Enrich People in Bulk

    This endpoint calls Apollo's POST /api/v1/people/bulk_match endpoint to enrich up to 10 people per request in a single call. Use it for large-scale enrichment workloads — for example, refreshing a contact warehouse or hydrating a backlog of leads — where the throughput improvement over the single-person endpoint significantly reduces wall-clock time.

    • Configure the upstream flow to deliver an array of person records under the details key — each entry follows the same shape as the single-person Enrich Person request body.
    • Enable record batching in the destination configuration (see Record Batching below) with a batch size of up to 10, and select the JSON property grouping algorithm to wrap batches under the details property in the outgoing request body.
    • Optional top-level reveal flags (reveal_personal_emails, reveal_phone_number) apply to every record in the batch.

    Apollo caps the bulk endpoint at 10 records per request and applies stricter rate limits (50% of the per-minute limit of the single-person endpoint). For full reference, see the Apollo Bulk People Enrichment documentation.

    Enrich Person by Domain

    This endpoint calls Apollo's POST /api/v1/people/match endpoint configured for domain-based matching. Use it when only a company email domain and basic person identifiers (name) are available — for example, when enriching webform submissions that include a work email but no LinkedIn URL.

    • Each upstream record must include a domain field (the company's email domain, for example example.com) together with first_name and last_name.
    • The full upstream record is sent as the JSON body of the POST /people/match request — Apollo's match logic uses the supplied domain to narrow the candidate set before scoring the name match.

    Domain-based matching produces the highest confidence results when the supplied domain is the company's primary corporate domain (not a free-email domain such as gmail.com). For mismatched or generic domains, expect lower match rates.

    Enrich Organization

    This endpoint calls Apollo's POST /api/v1/organizations/enrich endpoint to enrich a company record with Apollo's firmographic, technographic, and funding data. Use it to fill in company size, industry, location, technology stack, and revenue fields for inbound accounts, target lists, or existing CRM records.

    • Each upstream record must include a domain field (for example, apollo.io) or an Apollo organization id. The domain is the most common matching key and is generally easier to source from CRM data.
    • The full upstream record is sent as the JSON body of the POST /organizations/enrich request.

    Organization enrichment consumes Apollo credits. For full reference on returned fields (including industry, technologies, funding rounds, and revenue estimates), see the Apollo Organization Enrichment documentation.

Configure Manually​

Apollo destinations can be manually configured to send data to any valid Apollo API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Apollo API after each call to a new Nexla webhook data source — useful for chaining enrichment runs into downstream warehouses or follow-up flows.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Apollo API from the Method pulldown menu. Apollo's write and enrichment endpoints use:

    • POST: Used by all enrichment endpoints (/people/match, /people/bulk_match, /organizations/enrich), most create endpoints, and search endpoints
    • PUT: Used by Apollo's update endpoints (for example, /contacts/{id})
    • DELETE: Used by destructive endpoints such as removing a contact from a sequence

Data Format​

  1. Select the format in which the Nexset data will be sent to the Apollo API from the Content Format pulldown menu. Apollo's API accepts and returns JSON exclusively — select JSON so Nexla automatically serializes each Nexset record to the JSON body expected by Apollo.

API Endpoint URL​

  1. Enter the URL of the Apollo API endpoint to which you want to send the Nexset data in the URL field. The Apollo API base URL is https://api.apollo.io/api/v1/ and all endpoint paths are appended after it. For update/upsert operations such as PATCH /contacts/{id}, include the ID of the object to be updated at the end of the URL — Nexla can substitute the ID directly from an upstream record using a lookup-based macro.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Common headers for Apollo include Content-Type:application/json and Cache-Control:no-cache.

    You do not need to include the X-Api-Key header — Nexla attaches the API key from the credential automatically.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Apollo destination, select the attributes from the Exclude Attributes pulldown menu. This is useful for stripping internal metadata fields (for example, source IDs or processing timestamps) that should not be forwarded to Apollo.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching. Batching is required when targeting Apollo's bulk endpoints, including POST /people/bulk_match.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. For Apollo's bulk people match endpoint, set this to 10 — Apollo rejects bulk requests containing more than 10 records.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. For Apollo's bulk endpoints, select the JSON property algorithm and set the property name to details, which produces a request body of the form {"details": [ ... ]} as required by the bulk match endpoint.

Response Webhook​

Optional

Nexla can automatically send the response received from the Apollo API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, capturing each enrichment response (including matched person/organization details) into a downstream warehouse for analytics.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Apollo API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Apollo API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Apollo API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Apollo endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Apollo until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.