ZoomInfo
Enrich contacts and companies inside any workflow, using the organization's own ZoomInfo account.
Three ways to connect
| Method | Use it when |
|---|---|
| ZoomInfo Sign-in | A user can sign in to ZoomInfo. There is no app to create and no key to copy. |
| OAuth App | The org wants its own ZoomInfo app, with requests attributed to an integration user. The ZoomInfo plan must include API access. |
| Private Key | The ZoomInfo plan includes Enterprise API access. |
A user holds one ZoomInfo connection at a time. To change method, delete the connection under Connections and connect again.
Connect Floqer via ZoomInfo Apps
Requirements:
- A ZoomInfo user account with enrichment access.
Connect in Floqer with ZoomInfo Sign-in
-
Log in to app.floqer.com, go to Connections → ZoomInfo, and select ZoomInfo Sign-in.

-
Optional: turn on Enable for Org to share the connection with everyone in the organization.
-
Click Sign in with ZoomInfo.
-
Sign in to ZoomInfo with a user account that has enrichment access.
-
Review and approve the scopes Floqer requests. ZoomInfo asks only on the first sign-in.
Note
Floqer requests access to company data (api:data:company) and contact data (api:data:contact) only.
Reconnect
If Floqer asks for the connection to be reconnected, open Connections → ZoomInfo, click the pencil next to the connection, and click Reconnect.

Note
Only the user who connected can reconnect.
Connect with an OAuth App
To use OAuth, create a new app in ZoomInfo and paste its Client ID and Client Secret into Floqer.
Requirements:
- A ZoomInfo plan with API access: Enterprise API, Copilot, or a GTM.ai self-serve plan. The ZoomInfo account manager can confirm this.
- Access to the ZoomInfo Developer Portal. Enterprise customers who do not have it should ask their ZoomInfo admin. GTM.ai self-serve customers create apps from the Developer tab inside GTM.ai instead.
Create the app in ZoomInfo
- Open the app creation screen:
- Enterprise customers sign in to the ZoomInfo Developer Portal and click Create App.
- GTM.ai self-serve customers open the Developer tab in GTM.ai and click Create.
- Name the app
Floqer. - Under authentication, choose Client Credentials Flow.
- Select an integration user. ZoomInfo attributes every Floqer request to this user, and that user's access decides which fields come back, so pick one with enrichment access.
- Under scopes, tick Company (
api:data:company) and Contact (api:data:contact). - Click Create App and copy the Client ID and Client Secret that ZoomInfo shows.
Note
Do not submit the app for partner review or tick Ready To Publish. It is a Standard App for the organization's own use.
Connect in Floqer with an OAuth App
Log in to app.floqer.com, go to Connections → ZoomInfo, and keep the OAuth App tab selected.
| Field | What to enter |
|---|---|
| Client ID | The Client ID from step 6 above |
| Client Secret | The Client Secret from step 6 above |
- If other people in the org need this connection, turn on Enable for Org. Leave it off to keep the connection private to the connecting user.
- Click Connect to ZoomInfo.
Connect with a Private Key
Only use this method if the ZoomInfo contract still includes the Enterprise API.
Generate the key in ZoomInfo
- Sign in to the ZoomInfo Admin Portal as an admin.
- Go to Integrations → API & Webhooks and click Generate New Token. On older ZoomInfo accounts this screen is Admin Portal → API and the button is Generate New Key.
- Copy the Client ID and the Private Key, and store them securely. ZoomInfo shows the Private Key once. If it is lost, generate a new token.
Careful
The Private Key is not the Client Secret. It is a long multi-line block that starts with -----BEGIN PRIVATE KEY-----. Pasting the Client Secret saves fine but can never authenticate.
Connect in Floqer with a Private Key
Go to Connections → ZoomInfo, switch to the Private Key tab, and fill in three fields:
| Field | What to enter |
|---|---|
| UserEmail | The email address the ZoomInfo account signs in with |
| Client Id | The Client ID from step 3 above |
| Private Key | The whole private key block, BEGIN and END lines included |
- The key never expires. ZoomInfo recommends replacing it every 90 days. Generating a new token invalidates the previous one.
- To replace it, open the connection, paste the new key, and click Save Changes. Floqer caches the ZoomInfo access token for up to an hour, so workflows pick up a replaced key within that window.
Check that it works
Add ZoomInfo: Company Enrich to a workflow, map Company website to a column, and run one row. A new match costs one ZoomInfo credit.
Careful
A populated Input Fields dropdown is not proof. It falls back to a built-in list when Floqer cannot reach ZoomInfo. Only a row that returns data confirms the connection. For Company Enrich the dropdown comes up empty instead, which also means Floqer could not reach ZoomInfo.
The two actions
Both sit under People Data → People Enrichment in the action picker. Each is also listed a second time: Contact Enrich under People Data → Contact Enrichment, Company Enrich under Company Data → Company Enrichment. Same action either way.
| Action | Returns |
|---|---|
| ZoomInfo: Contact Enrich | Work email, direct and mobile phone, job title, management level, employment history, location, plus the company fields below |
| ZoomInfo: Company Enrich | Domain, revenue, employee count, industry, SIC and NAICS codes, social URLs |
- Map one input or several. Email alone works, so does name plus company.
- More inputs usually match better. At least one must have a value.
- Fields the package excludes are dropped automatically, and re-checked daily.
Credits
- ZoomInfo actions cost 0 Floqer credits.
- ZoomInfo charges one of its own credits the first time a record is enriched. Re-enriching that record is free on their side for the next twelve months, though it still counts toward the account's Records Under Management.
- On an OAuth App connection, ZoomInfo attributes usage to the integration user chosen when the app was created.
- On a ZoomInfo Sign-in connection, requests run as the ZoomInfo user who signed in.
- Floqer caches results, so repeating an action over the same inputs sends no new request.
Troubleshooting
| Message | What to do |
|---|---|
ZoomInfo authorization was declined. or ZoomInfo authorization failed: ... | The request was not approved on ZoomInfo's page, so nothing was saved. Click Sign in with ZoomInfo again and approve it |
ZoomInfo authorization expired or belongs to another workspace. Please connect again. | The sign-in took longer than ten minutes, or the user changed workspace part-way through. Start again from Connections → ZoomInfo |
Invalid ZoomInfo callback. Please connect again. | The page was opened without a response from ZoomInfo, for example from a bookmark or the browser's back button. Start again from Connections → ZoomInfo |
ZoomInfo token refresh was interrupted. Please reconnect ZoomInfo. | Floqer could not confirm the renewed access with ZoomInfo and will not reuse the old one. The user who connected opens the connection and clicks Reconnect |
Only the owner can reconnect this ZoomInfo connection. | The connection is shared by a teammate. Ask the user who connected it to reconnect |
ZoomInfo connection is no longer shared with this workspace. | The owner turned off Enable for Org. Ask the owner to turn it back on, or connect ZoomInfo separately |
Connection failed: ... with an error from ZoomInfo | The Client ID or Client Secret is wrong, or the app was created with a different authentication method. Re-copy both values from the app's page in the Developer Portal and check it uses Client Credentials |
HTTP 403 on an OAuth App connection | Either the app is missing a scope (ZoomInfo answers This application does not have the required scope; edit the app in the Developer Portal and tick both api:data:company and api:data:contact), or the ZoomInfo subscription does not include the API (ZoomInfo answers You do not have access to this endpoint) |
HTTP 403 on a Private Key connection | ZoomInfo has withdrawn Enterprise API access for the subscription. Remove the connection and connect with an OAuth App instead |
HTTP 401 on a Private Key connection | Credentials rejected. Check the key is the private key and is still active in ZoomInfo |
Client authentication failed, invalid_client, or ZoomInfo token request failed (HTTP ...) on an OAuth App connection | Floqer refreshes the token automatically, so this means the Client Secret was rotated or the app was deleted in the Developer Portal. Remove the connection and connect again with the current values |
The ZoomInfo app has neither the api:data:company nor the api:data:contact scope. | Edit the app in the Developer Portal, tick both scopes under Company and Contact, and connect again |
malformed plain PKCS8 private key(code:001) | The saved value is not a private key. Most often the ZoomInfo Client Secret was pasted into the Private Key tab. Either switch to the OAuth App tab, or re-copy the Private Key, BEGIN to END |
malformed PKCS8 private key(code:003) | The key is PKCS#1. Use the block starting with BEGIN PRIVATE KEY, not BEGIN RSA PRIVATE KEY |
malformed plain PKCS8 private key(code:002) | The key is passphrase-protected. Generate an unencrypted key in ZoomInfo |
ZoomInfo API key not found | Reconnect ZoomInfo. Turn on Enable for Org if a teammate's workflow needs it |
All input fields are empty | Map a column that has data on that row |
ZoomInfo credit limit exceeded for this account (matchStatus LIMIT_EXCEEDED) | The ZoomInfo account is out of enrichment credits. Top up in ZoomInfo and run the failed rows again; Floqer does not retry them |
ZoomInfo rejected the match input (matchStatus INVALID_INPUT) | ZoomInfo could not use the mapped value. Check the column holds the right kind of data for that input |
No data found (matchStatus: ...) | No match at ZoomInfo. Normal for some rows. Map more inputs |
To cut access, delete the app or token in ZoomInfo, or delete the connection in Floqer under Connections. A ZoomInfo Sign-in connection has no app or token on the org's side, so delete the connection in Floqer.
Have a question that isn't answered here? Contact Floqer support at hello@floqer.com.