Your CRM is full of contacts whose job titles changed three months ago. ZoomInfo itself says static data exports go stale within weeks — and most teams enrich their leads exactly once, at import time, then work off the decaying copy forever.
On October 12, 2026, ZoomInfo (NASDAQ: GTM) shipped a verified n8n node through GTM.AI, its API and MCP layer. Instead of exporting a CSV, you call enrichment at run time, mid-workflow — and an n8n AI Agent can call it as a tool in the middle of a conversation.
This guide covers what the node does, how to install and credential it, and three patterns you can run today: run-time lead enrichment, intent-signal watching, and the agent-as-researcher pattern.
What ZoomInfo actually shipped
A verified node in n8n’s node directory, built and maintained by ZoomInfo itself. The verified badge matters: when the vendor maintains the node, it breaks less often and gets updated when the API changes, unlike community nodes maintained in someone’s spare time.
The node reads ZoomInfo’s GTM Context Graph — which ZoomInfo describes as covering more than 100 million companies, 500 million contacts, and billions of buying signals. Those are ZoomInfo’s figures, not mine; treat them as vendor claims and verify coverage against your own ideal customer profile before betting pipeline on it.
Per the October 12 announcement, the node can:
- Search contacts by company, title, seniority, and location
- Enrich contact and company records
- Search companies by size, revenue, and industry
- Monitor buyer intent, organizational changes, and news on target accounts
This is ZoomInfo’s third connector since July 27, 2026 — Zapier, then ClickUp (October 9), now n8n. The pattern is clear: enrichment is moving out of the spreadsheet and into the workflow.
Prerequisites
- A ZoomInfo plan with API access. The integration is available to joint ZoomInfo and n8n customers as of October 12, 2026 — you need both accounts.
- An n8n instance (Cloud or self-hosted) where you can install nodes.
- Your ZoomInfo API credentials, from the ZoomInfo admin panel.
- One honest note up front: this node is one day old as of this writing. I have not run it myself, and community reports don’t exist yet. The setup below follows n8n’s standard verified-node pattern, and operation names may shift as ZoomInfo iterates — check the node’s in-editor docs for the final list.
Step 1 - Install the verified ZoomInfo node
In the n8n editor, click + to add a node and search for “ZoomInfo”. Look for the verified badge on the result — that’s the one ZoomInfo builds and maintains — and install it.
You should see the ZoomInfo node appear in your node picker with the verified checkmark. If you see multiple ZoomInfo entries, the verified one is the only one you want; unverified copies are community forks with no update guarantee.
Step 2 - Connect your ZoomInfo credentials
Open the node, go to Credentials, and create a new ZoomInfo credential. Paste in the API credentials from your ZoomInfo admin panel and save.
Each workflow authenticates with your own ZoomInfo credentials, and ZoomInfo applies the same access control, data lineage, and audit logging to node calls that it applies on its other GTM.AI surfaces. That means enrichment activity shows up in ZoomInfo’s audit trail — good for compliance, and something to remember when you’re testing.
Warning: every n8n workflow holding ZoomInfo credentials becomes a permissions surface your security team has to inventory. Before you wire this into five workflows, list which workflows hold the credentials and assign an owner to each. A leaked n8n API key with ZoomInfo credentials attached is a data-export machine.
Step 3 - Enrich inbound leads at run time
This is the highest-value pattern and the one that kills the stale-export problem. The shape: Trigger → ZoomInfo node → CRM update.
A concrete setup: a form or CRM webhook fires when a new lead arrives. The ZoomInfo node takes the lead’s email domain or company name and returns the enriched company record — size, revenue, industry — plus the enriched contact record. The workflow writes that back to the CRM before sales ever sees the lead.
The decision that matters here is what to enrich and when. Don’t fire an enrichment call on every inbound row unconditionally — enrichment products are credit-based, and a spam wave of form fills will burn credits. Gate it: only enrich leads that match a basic filter (business email, target geography), and cap daily calls with an IF node or a counter in a Data Table.
If you want this pattern pre-built, our AI Lead Capture → Enrich → Score → CRM Routing template does capture → enrich → AI-score → route with a Slack alert. It uses an HTTP step for enrichment today — the ZoomInfo node is a drop-in replacement for that step.
Step 4 - Watch target accounts for intent signals
The second pattern is a watcher, not a reactor. Schedule Trigger → ZoomInfo node → Filter → alert.
Run it daily against your target account list: search companies by size, revenue, and industry to keep the list fresh, then pull intent signals, organizational changes, and news for each account. An IF node splits on signal strength — a leadership change plus a spike in intent research goes to Slack immediately; a slow news week gets logged to a sheet for the weekly review.
This is where the “billions of buying signals” claim either earns its keep or doesn’t. Start with ten accounts you already know well and compare the node’s signals against what your reps actually hear on calls. If the signals don’t predict real conversations, don’t scale the watcher to five hundred accounts.
Step 5 - Hand the node to your AI agent as a tool
This is the headline capability: an n8n AI Agent calling ZoomInfo mid-conversation.
Add the ZoomInfo node as a tool sub-node under your AI Agent node. The step most people skip is the tool description — the agent decides when to call the tool based on that text. Write it plainly: “Look up the company behind an email domain: returns company size, industry, revenue, and key contacts. Use before drafting any prospecting reply.”
Now the agent can do something no static enrichment ever could: a prospect writes in, the agent looks up their company, and the reply references their actual industry and size — all inside one workflow execution. No export, no sync job, no stale copy.
One guardrail: give the agent the search and enrich operations, not the whole node. An agent with a monitoring operation and a daily schedule is a loop you didn’t ask for.
What I couldn’t verify
Three honest gaps, because this node is a day old:
- Credit metering. I don’t have ZoomInfo’s per-call credit costs for the node. Confirm how enrichment calls are metered on your plan before you point a high-volume trigger at it.
- Coverage for your market. The 100M companies / 500M contacts figures are ZoomInfo’s marketing. If you sell outside North America and Western Europe, test coverage on your actual ICP list first.
- Self-hosted edge cases. The announcement covers n8n broadly. If you self-host behind a firewall, confirm outbound access to ZoomInfo’s API endpoints from your n8n host.
FAQ
Do I need both a ZoomInfo account and n8n?
Yes. The integration is available to joint ZoomInfo and n8n customers. The node is useless without ZoomInfo API credentials, and ZoomInfo’s API without a workflow engine is just another tab.
Is this better than calling the ZoomInfo API with an HTTP Request node?
For most teams, yes — and the reason is maintenance, not features. A verified, vendor-maintained node gets updated when the API changes; your hand-rolled HTTP node breaks silently on the same day. If you already have a working HTTP integration, there’s no urgent reason to migrate.
Can the n8n AI Agent really call it as a tool?
That’s what the announcement states: an n8n AI agent can call the node partway through a workflow to research a company, enrich a contact, or check an intent signal. Treat the tool description as the actual interface — vague descriptions get vague tool use.
Key Takeaways
- ZoomInfo shipped a verified, vendor-maintained n8n node on October 12, 2026 — enrichment at run time instead of stale CSV exports.
- The node covers search, enrichment, and intent monitoring — contacts by title/seniority, companies by size/revenue/industry, plus buying signals and account news.
- An n8n AI Agent can call it as a tool mid-conversation — prospect research without leaving the chat.
- Inventory your credential surfaces — every workflow holding ZoomInfo credentials needs an owner before you scale.
- Verify the vendor’s coverage claims against your ICP before betting pipeline on the signals.
Next: install the node on a non-production n8n instance, run the Step 3 enrichment pattern against ten known leads, and compare the returned firmographics against what you already have. If the data is fresher than your CRM, you have your migration case.
Images: Pexels (Thirdman, Brett Sayles).