ZoomInfo Feeds

ZoomInfo is a B2B data platform that provides contact, company, intent, technographic, and news (scoops) intelligence for go-to-market teams. The ZoomInfo Feeds connector is a source-only ELT connector that authenticates with ZoomInfo using JWT-based authentication and ingests ZoomInfo resources as scheduled feeds. It exposes ZoomInfo's Contacts, Companies, Intent Signals, Technographics, and Scoops resource types, and includes a ready-made Search Contacts feed with role, company, location, and technology filters. Each selected feed is full-refreshed on the configured schedule.

Power end-to-end data operations for your ZoomInfo Feeds API with Nexla. Our bi-directional ZoomInfo Feeds connector is purpose-built for ZoomInfo Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ZoomInfo Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ZoomInfo Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The ZoomInfo Feeds connector authenticates with a ZoomInfo username and password. On each run, Nexla posts these credentials to ZoomInfo's /authenticate endpoint, receives a short-lived JSON Web Token (JWT), and sends that token as a bearer token on all subsequent API requests. ZoomInfo JWTs expire after 60 minutes; Nexla requests a fresh token automatically, so no manual token handling is required.

Before creating a ZoomInfo Feeds credential in Nexla, confirm the following:

1. You have an active ZoomInfo account with API access enabled. API access is a licensed capability — if you are unsure whether your subscription includes it, contact your ZoomInfo account administrator or ZoomInfo support.

2. You have a ZoomInfo username (the login email or username for the account) and its password. Nexla uses these to obtain a JWT from the ZoomInfo authentication endpoint.

3. The account has permission to query the ZoomInfo resources you intend to ingest (for example, contact and company search).

ZoomInfo also supports a client ID and private-key (key pair) authentication method, which is recommended for production automation because it does not require storing user credentials. This Nexla connector uses the username and password (JWT) method. Use a dedicated integration account where possible, and rotate the password periodically.

For more information, see the ZoomInfo API documentation and the ZoomInfo API reference.

Authenticate

Credentials required

Authenticate using ZoomInfo username and password to retrieve a JWT token.

Field	Required	Secret	Description
ZoomInfo Username	Yes	No	ZoomInfo Username
ZoomInfo Password	Yes	Yes	ZoomInfo Password

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

   Resource descriptions are recommended but are not required. Use them to identify the ZoomInfo account or access level represented by this credential.

3. Enter your ZoomInfo login username in the ZoomInfo Username field.

4. Enter the password for that account in the ZoomInfo Password field. Nexla stores this value securely and uses it, together with the username, to retrieve a JWT from the ZoomInfo /authenticate endpoint each time the source runs.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with ZoomInfo Feeds flows.

Use as a data source

How This Connector Works

The ZoomInfo Feeds connector is a source-only, ELT connector. Rather than configuring one REST endpoint at a time, you select the ZoomInfo resource you want to ingest, and Nexla loads it as a feed on a schedule.

• JWT authentication: On each run, Nexla exchanges your ZoomInfo username and password for a short-lived JWT and uses it as a bearer token for all requests. Token refresh is handled automatically.

• Discovery: The connector exposes a fixed list of ZoomInfo resource types available via the API. You choose which resource to load when configuring the feed.

• Full refresh: Feeds are ingested using a full-refresh strategy, so each run reads the current set of records for the selected resource. The id field is used as the primary key to uniquely identify records within a feed.

• Pagination: Feeds that return paged results (such as Search Contacts) are paged automatically until no further records are returned.

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

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

Select the Objects to Ingest

The connector exposes the following ZoomInfo resource types. Select the resource you want a feed to load:

• Contacts — ZoomInfo contact records.
• Companies — ZoomInfo company records.
• Intent Signals — Buyer intent data.
• Technographics — Technology install and usage data.
• Scoops — ZoomInfo Scoops (news and business-signal records).

Feed configuration

The following feed templates are available. Click a template to view its configuration details.

ZoomInfo Feed Loader

Generic feed loader for ZoomInfo APIs based on the selected resource type. Use this template to load any of the available ZoomInfo resources by pointing the feed at the appropriate API endpoint path and data path.

• Data Refresh Type — Choose the type of refresh to perform. The available option is Full Refresh, which reads the complete current set of records on each run.
• Endpoint Path — The ZoomInfo API endpoint path to call, appended to the ZoomInfo API base URL. Examples include search/contact, company, and intent.
• Query Parameters — An optional query string used to filter the data returned by the endpoint. Leave blank to fetch unfiltered results.
• JSONPath to Data — The path to the data objects within the API response. The default is $.data[*].
• Primary Key — The field used for deduplication or upsert. The default is id.

Field names and response paths vary by ZoomInfo resource. For endpoint paths, request bodies, and response structures, see the ZoomInfo API reference.

Search Contacts

Search ZoomInfo contact records based on role, company type, location, and technology filters. This feed calls the ZoomInfo contact search API and pages through results automatically until no further records are returned.

• Management Level — Optional. Filter contacts by management level (for example, directors, managers, or VP).
• Company Type — Optional. Filter by company type, such as public or private.
• ZIP Code — Optional. A ZIP code used for location filtering.
• ZIP Radius (mi) — Optional. The radius, in miles, around the specified ZIP code.
• Location Search Type — Optional. How location filtering is applied. The default is PersonAndHQ.
• Technology Attributes — Optional. A comma-separated technology tag list (for example, 333.202.*).
• Results Per Page — Optional. The number of records returned per page (for example, 10, 25, or 50). The default is 10.

All filters on this feed are optional. Leaving a filter blank widens the search. For the full list of supported contact search filters and their accepted values, see the ZoomInfo API reference.

Once the selected feed template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

ZoomInfo Feeds data sources can also be manually configured to ingest data from any valid ZoomInfo API endpoint, including endpoints not covered by the pre-built feed templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ZoomInfo Feeds data source. Nexla will now begin ingesting data from the configured feed and will organize any data that it finds into one or more Nexsets.