Correct ZoomInfo integration page

[claude]

Summary

Corrects the ZoomInfo integration page. This PR originally documented the new ZoomInfo GTM (OAuth) integration as available; it is not, so that content has been removed and the existing page fixed instead.

Why the OAuth content was pulled

The zoominfo_gtm provider and all six GTM tool steps are hidden behind the zoominfo-gtm-native feature flag (hideWhen: "when_disabled", default false) in both provider_feature_flag_visibility.ts and studio/transformations/feature_flag_visibility.ts.

The prod flag payload is {"force_internal_usage": true} — no projects map, no organizations map, no wildcard. Evaluated through IsFeatureEnabledForProjectOrOrg, that resolves true only for Relevance employees. No customer can see or connect the integration today, so documenting the OAuth flow, its tool steps, or an early-access path would have been wrong.

The OAuth documentation is written and sits in this branch's history (bbbf1e4). It can be restored once the flag payload has real orgs in it.

What this PR changes

• Removes four tool step cards that document nothing. Search contacts, Search companies, Enrich contact, and Enrich company are not in the transformation registry. On the credential-based integration, only zoominfo_api_call exists.
• Describes Zoominfo API call as the single step all ZoomInfo operations run through — search, enrichment, and lookup are reached by pointing it at an endpoint.
• Drops the "select your connected ZoomInfo account from the dropdown" instruction. zoominfo_api_call has no oauth_account_id field; authorization comes from the project credentials.
• Replaces the API call example, which used a /companies/enrich endpoint and an include_attributes body that do not exist, with a lookup call taken from the step's own field hint.
• Removes the "built-in credit safeguards" claim (two places) — no supporting code.
• Adds one FAQ noting an OAuth version is in development and not yet available. No timeline, no enablement path.
• Capitalizes Agents and GTM Agents per the docs style rules.

The credential-based connection instructions are unchanged.

Linear issue

https://linear.app/relevance/issue/TSP-1326/

TSP-1326 is not fully closed by this PR — the GTM OAuth documentation is still owed and is blocked on the flag rollout.

[linear]

TSP-1326

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
relevanceai	🟢 Ready	View Preview	Jul 1, 2026, 5:57 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[github-actions]

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	"Agent" is a Relevance AI product proper noun but written lowercase throughout ("your AI agents", "GTM agents"). "Taxonomy Lookup" vs "Taxonomy lookup" inconsistent between Card title and prose.
🟡	Technical clarity	7/10	Both custom API Call sections tell users to configure parameters "according to the ZoomInfo API documentation" but never link to it — Apollo.mdx links out to Apollo's API docs in the same section pattern. Technical users are left to find ZoomInfo's docs themselves.
🟢	Non-technical clarity	9/10	Credit model (search free / enrich costs credits) is explained clearly and reinforced throughout. GTM vs legacy distinction is well framed.
🟢	Structure	9/10	Solid integration page. One numbered list that should be <Steps>.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: A well-written, well-structured integration page — the credit consumption section in particular is genuinely useful and the GTM vs legacy framing is clear. Main gaps are the "Agent" capitalization inconsistency (present throughout) and a missing link to ZoomInfo API docs that will leave advanced users hunting.

🔧 Issues (6)

• integrations/popular-integrations/zoominfo.mdx:3 — frontmatter description: "from your AI agents" → "from your AI Agents" — Agent is a Relevance AI product proper noun and should be capitalized when referring to the product feature.
• integrations/popular-integrations/zoominfo.mdx:7 — "your AI agents can search ZoomInfo's database" → "your AI Agents" — same rule; this is referencing the product feature.
• integrations/popular-integrations/zoominfo.mdx:147 — <Card title="Taxonomy lookup"> — the prose throughout the page consistently refers to this as "Taxonomy Lookup" (capitalized, treating it as the proper name of the tool step — e.g. lines 311, 348). Card title should match: "Taxonomy Lookup".
• integrations/popular-integrations/zoominfo.mdx:217 — "Set the HTTP method, endpoint path, and request body parameters according to the ZoomInfo API documentation." — no link to ZoomInfo API docs. Apollo.mdx links directly to Apollo's API docs in the equivalent step ([Apollo's API documentation](https://apolloio.github.io/apollo-api-docs/)). Same issue on line 265 (legacy equivalent).
• integrations/popular-integrations/zoominfo.mdx:295 — Accordion title "GTM agent prospect research" → "GTM Agent prospect research" — Agent is the Relevance AI product proper noun.
• integrations/popular-integrations/zoominfo.mdx:363–364 — FAQ accordion title "Does ZoomInfo work with GTM agents?" and body "compatible with GTM agents in Relevance AI" → "GTM Agents" — same capitalization rule.

🧩 Component suggestions (1)

• integrations/popular-integrations/zoominfo.mdx:188–196 — "How to add ZoomInfo tool steps to your agent" is a six-step sequential procedure written as a plain numbered list. Every other sequential procedure on this page uses <Steps> (the GTM OAuth setup, the legacy credential setup, both API Call sections). Wrap this in <Steps> for visual consistency and to match the page's own pattern.

✅ Clean files (0)

All issues are in integrations/popular-integrations/zoominfo.mdx.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~888

Files read: integrations/popular-integrations/zoominfo.mdx (375 lines), integrations/popular-integrations/apollo.mdx (165 lines), integrations/popular-integrations/lusha.mdx (348 lines)