Perplexity

Overview

ZoomInfo is a native connector in Perplexity. Paid Perplexity users with access to Perplexity Computer can add ZoomInfo from the Connectors menu and route research questions through ZoomInfo's MCP tools alongside Perplexity's own web search.

The connector works with whichever model you select inside Perplexity, including Perplexity's default model and third-party options like Anthropic.

Setup

Next - run your first session. Once ZoomInfo is connected, paste this into Perplexity. It orients from your GTM context and only runs after you approve:

(Use the ZoomInfo MCP tools if available; otherwise use the GTM CLI. Use the tool schema or CLI help for supported commands.)

I just connected ZoomInfo. Help me complete the job below.

1. Read my saved business context with get_gtm_context, or the CLI equivalent. This read is free. Use the returned offerings, ICP, and role to frame the work. If context is missing, continue with the information we have. Save changes only if I explicitly ask; a first briefing does not require updating shared business context.

2. Prepare a connected account briefing. Ask me only which company or domain to brief if I haven't named one. Use the account and decision already in this conversation when available. Connect the account's available CRM history, including stage and status, with recent customer conversations and external buying signals. Use Account Research, and add Browse Engagements, Conversation Intelligence, or company signals when the briefing needs more evidence.
   Return a short briefing: where things stand, what changed, what remains unresolved, and one recommended next action. Cite the source and date for each material fact when returned. Distinguish the recommendation from the evidence.

3. Before calling a tool, check its schema or documented inputs rather than guessing at parameters. Ask only for missing inputs, in a single message, then name the tools and give a credit estimate if supported by their documentation. Label it as an estimate: actual charges depend on records and work done. Ask for approval once before paid research, then complete the selected job.

If a tool call comes back "No approval received" or a similar permission response, say so plainly, name the tool, and continue with the remaining steps. Don't retry the same call hoping for a different result, and don't invent an approval that didn't happen.

Include a source-coverage note of no more than 3 lines. Separate an unavailable or unauthorized source from a successful search with no matching records. If connection status is unknown, say so. Never infer "no customer history" from an empty result. Continue with available evidence and identify what is missing; use https://gtm.ai/guides/connect-customer-context for source setup.

Recommend CRM changes as drafts. Applying them requires an available, separately connected CRM workflow and my authorization. Do not claim a CRM update was made by ZoomInfo research tools.

Using ZoomInfo in a Prompt

Once the connector is on, Perplexity invokes ZoomInfo tools live and shows the calls inline. A prompt like:

Get me 5 contacts for Walmart with a phone number.

will run Search Contacts against ZoomInfo and return real records. You can chain follow-ups in the same conversation, and Perplexity carries the context forward.

For an account-style question:

What companies in Boston use Salesforce and have revenue greater than 20 million annually?

Perplexity routes through Search Companies with the right filters and returns matching records.

Tips for Best Results

Disable web search for pure ZoomInfo answers

Perplexity defaults to running its own web search alongside connectors. For prompts that should rely entirely on ZoomInfo (contact lookups, intent signals, account research), untick Web in the search options. The connector still runs.

Be explicit about what you want

Perplexity's router sometimes prefers public-domain answers over ZoomInfo when the prompt is ambiguous. Asking "What does the CEO of Costco care about?" may pull a mix of public sources and ZoomInfo data. Naming the tool ("research this account in ZoomInfo") or the data type ("pull intent signals for...") biases the router toward the connector.

Switch models for tougher work

From the model picker, you can swap Perplexity's default for Anthropic or another provider. Tool-use behavior is consistent across models. Reasoning and synthesis quality vary.

How Perplexity Selects Tools

Perplexity reads the ZoomInfo tool descriptions and picks the right one for your request. You don't need to specify which tool to call. New tools added to the ZoomInfo MCP server become available automatically; Perplexity refreshes the tool list at the start of each session.

Troubleshooting

ZoomInfo doesn't appear under Connectors: confirm you're on a paid Perplexity plan that includes Computer. Free plans don't expose the connector marketplace.

Authentication errors: make sure you're using your personal ZoomInfo credentials, not a shared or admin-only account. Disconnect and reconnect from Settings → Connectors if the token has gone stale.

Mixed results between public web and ZoomInfo: untick Web in the search options for the prompt. Web search runs in parallel by default and can dominate the answer when both sources have something to say.

Credit errors during enrichment: confirm your account has bulk data credits enabled. Recurring monthly credits are not supported by MCP.