Ellipse Gradient for Header

ZoomInfo Integration Guide

Integrate ZoomInfo company, contact, intent, technographic, and intelligence data with enterprise systems through authenticated REST APIs and scheduled Martini workflows.

ZoomInfo integration options at a glance

ZoomInfo’s documented integration model is centered on REST APIs for authentication, company and contact search, enrichment, and related data products. An authentication request returns a bearer token for subsequent calls. Martini can use workflows to retrieve Companies, Contacts, Intent, Technographics, Scoops, and enrichment results, then map and validate the responses for CRM, marketing, sales engagement, or data-platform targets. Scheduled processing is a practical default because general ZoomInfo webhooks, outbound callbacks, bulk APIs, and change-data-capture capabilities were not confirmed. Subscription entitlements, API limits, enrichment credits, filters, and endpoint availability should be validated for each account.

Integration pointSupported by ZoomInfo?Common use casesHow Martini supports it
REST APIsYesZoomInfo documents REST endpoints for authentication, company and contact search, enrichment, and related data products. REST is the primary mechanism for retrieving ZoomInfo intelligence.Martini can consume documented ZoomInfo REST endpoints from workflows, map JSON responses, apply business rules, and write results to downstream applications or databases.
AuthenticationYesZoomInfo documents an authentication request using account credentials that returns a bearer token for subsequent API calls.Martini can keep credentials in secrets management, call the authentication endpoint, pass the returned bearer token in the Authorization header, and manage token use within an integration workflow.
Company and contact searchYesSearch endpoints can support company and contact discovery using attributes such as domains, company names, geography, email addresses, or other endpoint-specific criteria.Martini can normalize lookup inputs, call search operations, validate response quality, and map Companies or Contacts into CRM, marketing, or data-platform schemas.
Enrichment APIsYesZoomInfo documents enrichment-style operations for appending or updating company and contact attributes, subject to licensed products, match rules, and usage credits.Martini can orchestrate enrichment calls, evaluate match confidence, prevent duplicate updates, apply field ownership rules, and record no-match or rejected outcomes.
Scheduled synchronizationLimitedA general change-data-capture or event stream was not confirmed, so scheduled API retrieval is a practical synchronization approach. Date, update, and search filters must be confirmed for each resource.Martini can trigger recurring workflows, preserve page or cursor state and execution checkpoints, and process data incrementally where the ZoomInfo endpoint supports suitable filters.
Bulk, asynchronous, or batch APIsNot confirmedThe reviewed documentation confirms search and enrichment operations but not a generally available bulk or asynchronous API. Batch limits, exports, formats, and credit rules require account-specific validation.Martini can orchestrate controlled batches over documented REST operations, but the workflow should not assume bulk support or bypass ZoomInfo usage limits.
Webhooks and outbound callbacksNot confirmedA general ZoomInfo webhook or outbound-callback capability was not confirmed. A callback should be used only if a specific licensed product documents it.If a documented callback is available for the customer’s product, Martini can receive it through a REST or webhook-oriented workflow; otherwise scheduled REST retrieval is the safer design.

How ZoomInfo exposes data and business events

ZoomInfo REST APIs

ZoomInfo’s documented REST APIs provide the primary integration surface for authentication, company and contact search, enrichment, and other licensed data products. Endpoint availability, fields, filters, limits, and credits can vary by subscription and account configuration.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with ZoomInfo, retrieves a bearer token, calls the required search or enrichment endpoint, handles pagination where applicable, validates the response, maps ZoomInfo objects to a canonical model, and writes the result to a target system or exposes it through a Martini API.

Implementation sequence

Authenticate with the ZoomInfo authentication endpoint
Store and apply the returned bearer token
Retrieve the required Companies, Contacts, Intent, Technographics, or Scoops data
Handle the endpoint-specific pagination or processing boundary
Validate matches, required fields, and entitlement-related responses
Map the response to the target application or canonical model

Scheduled ZoomInfo synchronization

A general ZoomInfo webhook, callback, event stream, or change-data-capture mechanism was not confirmed. Scheduled API retrieval is therefore a practical default for recurring enrichment and data synchronization, subject to supported endpoint filters.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a workflow, the workflow reads its last successful checkpoint, retrieves eligible pages or lookup candidates from ZoomInfo, applies matching and deduplication rules, persists successful results and processing state, and routes transient failures for controlled retry.

Implementation sequence

Start the workflow on a defined schedule
Read the last successful timestamp, cursor, page, or object identifier
Retrieve the next eligible ZoomInfo results
Apply matching, validation, and duplicate-prevention rules
Write approved results to the downstream system
Persist the checkpoint and record rejected or failed items

Common ZoomInfo integration patterns

Pattern 1: Enrich Salesforce Accounts and Contacts

When to use this pattern

Use this pattern when Salesforce is the system of record for prospects or customers and ZoomInfo is used to append firmographic or professional attributes. The design should define matching inputs, minimum confidence, field ownership, and behavior for no-match or ambiguous results.

Integration direction
Salesforce
Martini
ZoomInfo
Salesforce
Example Mapping
ZoomInfo FieldCanonical FieldTarget Field
Company domainorganization.domainAccount.Website
Employee countorganization.employeeCountAccount.NumberOfEmployees
Job titleperson.jobTitleContact.Title
Industryorganization.industryAccount.Industry
Martini implementation pattern

A scheduled Martini workflow retrieves candidate Salesforce Accounts, Leads, or Contacts, normalizes domains and email addresses, calls the applicable ZoomInfo search or enrichment endpoint, validates the match and confidence, and updates only approved Salesforce fields. It records no-match and ambiguous cases separately, respects Salesforce and ZoomInfo limits, and retries only transient failures that will not repeat a chargeable request incorrectly.

Martini capabilities used
  • workflows
  • scheduler triggers
  • API consumption
  • data mapping
  • validation
  • business rules
  • error handling

Pattern 2: Load ZoomInfo Companies and Contacts into HubSpot

When to use this pattern

Use this pattern when HubSpot needs enriched company and contact data for segmentation, campaign activation, or sales operations. The implementation should establish whether the company domain or contact email is the primary matching key and which system owns each field.

Integration direction
ZoomInfo
Martini
HubSpot
Example Mapping
ZoomInfo FieldCanonical FieldTarget Field
Company domainorganization.domainCompany.domain
Company nameorganization.nameCompany.name
Contact emailperson.emailContact.email
Employee countorganization.employeeCountCompany.numberofemployees
Martini implementation pattern

Martini can schedule ZoomInfo retrieval or enrichment, normalize and validate the response, apply rules that prevent ZoomInfo from overwriting authoritative HubSpot values, and create or update HubSpot objects using stable keys. The workflow persists synchronization state, captures rejected records, and uses bounded retries for temporary downstream failures.

Martini capabilities used
  • workflows
  • scheduled execution
  • API consumption
  • mapping and transformation
  • business rules
  • idempotency
  • error handling

Pattern 3: Route Intent Signals to Sales and Marketing

When to use this pattern

Use this pattern when available ZoomInfo Intent data should create account alerts, tasks, campaign memberships, or analytical events in Salesforce, HubSpot, Microsoft Dynamics 365, or a data warehouse. The exact filters and incremental-query options must be confirmed for the licensed endpoint.

Integration direction
ZoomInfo
Martini
Salesforce
Example Mapping
ZoomInfo FieldCanonical FieldTarget Field
Company identifieraccount.vendorIdAccount.ZoomInfoId
Intent topicintent.topicAccountIntent.Topic
Intent scoreintent.scoreAccountIntent.Score
Observation dateintent.observedAtAccountIntent.ObservedAt
Martini implementation pattern

A Martini scheduler queries the available Intent endpoint using supported filters, evaluates geography, industry, topic, and score rules, and creates a deduplicated alert or task for qualifying companies. A composite key such as company identifier, topic, and observation date prevents duplicate actions; the workflow stores the last successful query boundary and routes uncertain or failed items for review.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • conditional routing
  • data mapping
  • business rules
  • deduplication
  • checkpoint persistence

Pattern 4: Expose a Controlled ZoomInfo Data Service

When to use this pattern

Use this pattern when multiple internal applications need ZoomInfo data but should not each manage ZoomInfo credentials, resource-specific mappings, rate controls, and entitlement behavior. Martini provides a controlled internal API abstraction over selected ZoomInfo operations.

Integration direction
Internal Applications
Martini
ZoomInfo
Example Mapping
ZoomInfo FieldCanonical FieldTarget Field
Lookup domainorganization.domainZoomInfo company search criteria
Contact emailperson.emailZoomInfo contact enrichment criteria
Company profileorganization.profileInternal API response.company
Enrichment resultenrichment.attributesInternal API response.attributes
Martini implementation pattern

A Martini REST API validates incoming requests, applies authorization and field-level rules, invokes reusable workflow logic that authenticates with ZoomInfo, shapes the response, and returns only approved data. Centralized logging, throttling controls, mapping, retries, and error classification keep vendor-specific behavior out of consuming applications.

Martini capabilities used
  • API exposure
  • workflows
  • API consumption
  • request validation
  • data mapping
  • secrets management
  • error handling

Applications commonly integrated with ZoomInfo

ZoomInfo data can be incorporated into sales, marketing, engagement, workflow, and analytics architectures. The exact endpoints, fields, and commercial entitlements should be validated against the customer’s ZoomInfo subscription before implementation.

Application Scenario Direction Martini Pattern
Salesforce Enrich Accounts, Leads, and Contacts with company and contact intelligence, and route qualifying Intent signals to sales users. Salesforce → Martini → ZoomInfo A Martini workflow retrieves candidate Salesforce records, normalizes domains or contact identifiers, calls the applicable ZoomInfo search or enrichment endpoint, validates match results, and writes approved fields back to Salesforce while recording unmatched and failed attempts.
HubSpot Enrich companies and contacts and support segmentation or campaign activation using firmographic, contact, and intent data. HubSpot → Martini → ZoomInfo Martini can schedule HubSpot record retrieval, use domains or email addresses for ZoomInfo lookups, apply field ownership rules, and update only approved or empty HubSpot fields with validated enrichment results.
Microsoft Dynamics 365 Append firmographic and contact intelligence to Accounts, Contacts, and Leads used by sales teams. Microsoft Dynamics 365 → Martini → ZoomInfo A workflow can extract Dynamics identifiers and lookup attributes, call ZoomInfo REST endpoints, transform the response into Dynamics schemas, and apply matching, confidence, retry, and duplicate-prevention rules before updating records.
Marketo Use company, contact, and intent data for lead qualification, segmentation, and campaign activation. Marketo → Martini → ZoomInfo Martini can retrieve eligible Marketo leads or accounts, enrich them through ZoomInfo, evaluate qualification rules, and send approved attributes or classifications back to Marketo with controlled scheduling and error handling.
Outreach Provide enriched prospect and account information for sales engagement workflows. ZoomInfo → Martini → Outreach Martini can retrieve or stage approved ZoomInfo Contacts and Companies, map them to Outreach prospect and account fields, validate required identifiers, and submit downstream updates with duplicate checks and retry handling.
Salesloft Improve prospecting lists and sales cadence enrollment with enriched company and contact data. ZoomInfo → Martini → Salesloft A Martini workflow can query or enrich ZoomInfo data, apply territory and qualification rules, transform approved prospects for Salesloft, and avoid repeated cadence enrollment through stable business keys.
Snowflake Centralize ZoomInfo data for analytics, account scoring, governance, and downstream activation. ZoomInfo → Martini → Snowflake Martini can schedule paginated ZoomInfo API extraction, persist raw and normalized payloads, track cursors or processing state, and write Companies, Contacts, Intent, Technographics, or Scoops to Snowflake using explicit schemas.
ServiceNow Add company or contact intelligence to customer, account, or workflow records where the business data model supports that use case. ZoomInfo → Martini → ServiceNow Martini can retrieve approved ZoomInfo data, transform it to the relevant ServiceNow tables or API payloads, validate identifiers and field ownership, and route rejected or ambiguous matches for review.

How to build a ZoomInfo integration in Martini

Objective

Establish authenticated access to ZoomInfo and the downstream application without embedding credentials in workflow definitions or source-controlled configuration.

Instructions in Martini

  • Store ZoomInfo account credentials and related tokens in Martini secrets management
  • Call the ZoomInfo authentication endpoint and capture the returned bearer token
  • Configure the target application authentication separately and validate access to required resources
  • Confirm licensed ZoomInfo products, endpoints, limits, and data or enrichment credits

Objective

Select a trigger that matches the available ZoomInfo capabilities and the required freshness of the integration.

Instructions in Martini

  • Use a scheduler for recurring search, enrichment, or synchronization workflows
  • Use an API-triggered workflow when an internal application submits a lookup or enrichment request
  • Use a ZoomInfo callback only when a specific product and contract document that capability
  • Define the execution interval, concurrency, and checkpoint strategy

Objective

Retrieve ZoomInfo data with endpoint-specific request parameters, pagination, and matching inputs.

Instructions in Martini

  • Normalize domains, company names, email addresses, or other lookup attributes before calling ZoomInfo
  • Call the required Companies, Contacts, Intent, Technographics, Scoops, search, or enrichment endpoint
  • Handle the endpoint-specific page, cursor, offset, or date filter behavior
  • Preserve the processing boundary and avoid unnecessary repeated enrichment requests

Objective

Coordinate authentication, retrieval, validation, transformation, target writes, and exception handling as a maintainable Martini workflow.

Instructions in Martini

  • Separate authentication, retrieval, mapping, business rules, and persistence into clear workflow stages
  • Classify no-match and ambiguous-match responses as controlled business outcomes
  • Apply bounded concurrency and backoff for throttling or temporary vendor failures
  • Persist request and processing state needed for safe restart and replay

Objective

Convert ZoomInfo’s vendor-specific response structures into a canonical model and target application schema.

Instructions in Martini

  • Map Companies, Contacts, Intent, Technographics, Scoops, and enrichment attributes explicitly
  • Normalize identifiers, domains, email addresses, enumerations, and dates
  • Apply field ownership rules so enrichment does not overwrite authoritative values unexpectedly
  • Validate required fields and match confidence before writing downstream data

Objective

Control which results are accepted, updated, routed, or rejected based on data quality, confidence, and commercial constraints.

Instructions in Martini

  • Define minimum match confidence and behavior for no-match or ambiguous results
  • Use stable company and contact keys to prevent duplicate creation
  • Filter Intent by supported topic, geography, industry, score, or other endpoint-specific criteria
  • Track rejected, skipped, and credit-sensitive operations for operational review

Common ZoomInfo data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
CompaniesOrganization profiles containing firmographic attributes, domains, industry information, headquarters, employee counts, and related company data.Salesforce, HubSpot, Microsoft Dynamics 365, Snowflake, ServiceNowMartini retrieves or enriches Companies through REST APIs, normalizes domains and identifiers, applies match and field-ownership rules, and maps the result to downstream schemas.
ContactsIndividual business contacts and professional attributes used for prospecting, enrichment, qualification, and sales engagement.Salesforce, HubSpot, Marketo, Outreach, SalesloftMartini can match Contacts using email, name, company, or vendor identifiers, validate ambiguous results, transform fields, and synchronize approved values.
IntentBuying-intent signals associated with companies, topics, or related activity for account prioritization and sales or marketing action.Salesforce, HubSpot, Microsoft Dynamics 365, SnowflakeMartini can query available Intent data, filter by topic, geography, industry, or score, create deduplicated alerts or tasks, and persist processing boundaries.
TechnographicsTechnology associations for companies, supporting segmentation, account scoring, and prospect qualification.Snowflake, Salesforce, HubSpot, MarketoMartini can retrieve Technographics where licensed, normalize technology values, apply inclusion or exclusion rules, and load the results into analytics or activation systems.
ScoopsCompany intelligence and business-event information used to identify relevant account developments.Salesforce, Snowflake, Microsoft Dynamics 365Martini can retrieve Scoops through available endpoints, map event attributes, apply relevance rules, and create downstream alerts or analytical records.
Company and contact enrichment dataEnrichment results that append or update attributes in an existing customer or prospect record.Salesforce, HubSpot, Microsoft Dynamics 365, MarketoMartini validates lookup inputs and match outcomes, applies confidence and field-ownership rules, updates only approved attributes, and records no-match or failed requests.

Authentication and security considerations

Authentication model

ZoomInfo documents an authentication request that accepts account credentials and returns a bearer token for subsequent API calls. OAuth 2.0, API keys, scopes, and a specific JWT format were not confirmed in the reviewed documentation.

Credential protection

  • Store ZoomInfo credentials and tokens in Martini secrets management.
  • Send the returned token in the Authorization header for authorized API requests.
  • Do not place credentials in workflow source, mappings, or plain-text configuration.
  • Restrict logging of authentication responses and sensitive contact data.

Access and data governance

API access may be governed by ZoomInfo subscription entitlements and enabled products. Review permissions, retention, regional handling, and access controls for company and contact intelligence before deployment.

Operational considerations for ZoomInfo integrations

Rate limits and credits

ZoomInfo usage may be constrained by account limits, subscription entitlements, and data or enrichment credits. Use controlled concurrency, caching where permitted, and backoff for throttling responses.

Pagination and checkpoints

Search and list operations should handle the pagination model defined by each endpoint. Persist the relevant page, cursor, offset, date boundary, or object identifier so a workflow can resume safely.

Matching and idempotency

Define deterministic matching rules for domains, company names, email addresses, and vendor identifiers. Use stable business keys and persisted state to prevent duplicate updates or repeated chargeable enrichment requests.

Schema and testing

Isolate ZoomInfo response schemas from downstream models, validate required fields and enumerations, and test entitlement, no-match, ambiguous-match, throttling, and response-change scenarios before production use.

Monitoring and retries

Classify failures by authentication, permissions, lookup quality, rate limits, vendor availability, and downstream status. Retry only transient failures, record rejected outcomes, and monitor both technical requests and commercial usage.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration beyond individual API calls

Scripts can call ZoomInfo, but Martini provides a maintainable workflow structure for authentication, pagination, matching, enrichment, transformation, downstream writes, and exception handling.

Reusable integration assets

Martini can expose a controlled REST API or reusable workflow logic so internal applications do not each manage ZoomInfo credentials, vendor-specific schemas, rate controls, and entitlement behavior.

Reliable data movement

  • Schedule recurring retrieval when general webhook coverage is unavailable.
  • Apply explicit mappings, validation, field ownership, and business rules.
  • Persist checkpoints and idempotency keys for safe restart and duplicate prevention.
  • Centralize error classification, bounded retries, logging, and operational monitoring.

Flexible targets

Martini can transform ZoomInfo JSON responses for CRM, marketing, sales engagement, data warehouse, database, or internal API targets without coupling every application directly to ZoomInfo.

Frequently asked questions

How can ZoomInfo be integrated with enterprise systems?

ZoomInfo can be integrated through its documented REST APIs for authentication, company and contact search, enrichment, and related data products. Enterprise workflows can retrieve Companies, Contacts, Intent, Technographics, or Scoops, transform the results, and write them to CRM, marketing, sales engagement, analytics, or data-platform systems. The available endpoints and fields depend on the customer’s subscription and account configuration.

Can Martini integrate with ZoomInfo?

Yes. Martini can integrate with ZoomInfo by consuming its documented REST APIs, authenticating through the ZoomInfo authentication endpoint, passing the returned bearer token, and orchestrating search or enrichment workflows. Martini can map and validate the results for systems such as Salesforce, HubSpot, Microsoft Dynamics 365, Marketo, Snowflake, or other supported targets.

Do I need a connector to integrate ZoomInfo with Martini?

No. A dedicated ZoomInfo connector is not required. Martini can use ZoomInfo’s confirmed native REST APIs and authentication mechanism through API-consuming workflows. A native Martini ZoomInfo connector was not confirmed, and webhook or callback use should be limited to any specific ZoomInfo product that documents that capability.

Is there any extra Lonti cost to integrate ZoomInfo with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate ZoomInfo with Martini. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ZoomInfo, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which ZoomInfo integration methods should be used?

REST APIs are the primary documented integration method for ZoomInfo authentication, search, enrichment, and related data products. A general GraphQL API, SOAP API, webhook system, outbound callback mechanism, bulk API, asynchronous API, file API, or direct database access was not confirmed in the reviewed documentation. Martini can also expose a controlled REST API façade for internal consumers.

Can ZoomInfo push events or webhooks to Martini?

A general ZoomInfo webhook, outbound-callback, event-stream, or change-data-capture capability was not confirmed. Implementations should generally use scheduled REST API workflows. If a specific licensed ZoomInfo product documents a callback feature, Martini can receive and process that notification through an appropriate API or webhook-oriented workflow.

How does synchronization and data mapping work with ZoomInfo?

Martini can schedule ZoomInfo API retrieval, handle endpoint-specific pagination or filters, map vendor objects to a canonical model, apply matching and field-ownership rules, and write approved results to downstream systems. Stable keys such as company domains, vendor identifiers, contact email addresses, or composite Intent keys can support idempotency. Incremental processing should only be described where the licensed endpoint supports suitable date or update filters.

How are ZoomInfo errors, retries, and duplicates handled?

A Martini workflow can distinguish authentication, entitlement, invalid lookup, no-match, ambiguous-match, rate-limit, temporary vendor, and downstream failures. Retries should be bounded and limited to transient conditions, especially where enrichment requests may consume credits. Stable business keys, persisted checkpoints, response hashes, and controlled updates help prevent duplicate Companies, Contacts, or Intent actions.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Build a maintainable ZoomInfo integration with Martini

Use Martini to connect ZoomInfo REST APIs with CRM, marketing, sales engagement, analytics, and data-platform workflows while centralizing authentication, mapping, validation, scheduling, and operational error handling.

EXPLORE MARTINI
BOOK A DEMO