docs(using-clay-in-chatgpt): add pagination step, update example prompts, expand FAQ answers

[george-dilthey]

What changed

Added a new step 5 to the "Getting started" section documenting that results are returned in groups of 20 with a "Load more" button for additional pages; renumbered the former step 5 ("Open in Clay") to step 6. Updated the third example prompt in "Find and enrich people" from a people-search example to a company-search example (@Clay Find healthcare technology companies in the US...), with an explicit beta note: "Company search is currently rolling out — contact support to enable if it's not yet available in your workspace." Updated the "Do I need a paid ChatGPT plan?" FAQ answer from a single sentence to a fuller explanation. Updated best practices to use backtick formatting for rippling.com and removed the "Limit your search to one company at a time" bullet. All changes are in docs/using-clay-in-chatgpt.md.

Why

Triggered by a Webflow collection_item_published webhook for https://university.clay.com/docs/using-clay-in-chatgpt. Upstream Webflow page changed; the following substantive deltas were identified and applied surgically, preserving local enrichments (the Audiences FAQ, the enriched company-search FAQ, the email-context note in draft outbound, and the detailed credit FAQ answers).

Local enrichments NOT overwritten:

• The Note about email copy being filled with Clay workspace business context (removed upstream, kept locally as it's useful context)
• The "Can I search for companies?" FAQ enriched local answer (already confirmed company search and has more detail than new upstream text)
• The "Can I query my Audiences data..." FAQ (local-only, not in upstream)
• The enriched credit FAQ answers with "welcome bonus" framing
• The "If I send outreach..." verbose explanation (upstream simplified but local has more useful detail)

Source link(s)

• Webflow webhook source: https://university.clay.com/docs/using-clay-in-chatgpt
• Pagination claim (PASS after correction): /workspace/clay-base/apps/api/v3/mcp/constants.ts:260 (MAX_CONTACTS_COUNT = 20), /workspace/clay-base/apps/mcp-frontend/components/widgets/SearchResultsPager.tsx:63 (Load more button label). Upstream said "up to 100 results total" which was WRONG (code cap is 10,000); corrected to omit the cap.
• Company search example prompt (BETA): Code-confirmed at /workspace/clay-base/apps/api/v3/mcp/constants.ts:38 (SearchCompanies tool registered) and libs/api-contract/src/chatgpt-app/interfaces.ts:55–68 (company filters schema). Behind Eppo flag EnableDecoupledMcpToolsChatgpt (default off for ChatGPT); GA targeted July 21 per Slack. Beta framing added inline in the doc.
• Free ChatGPT plan FAQ: Clay's code does not gate on ChatGPT plan type (no plan check in /workspace/clay-base/apps/api/v3/mcp/); the expanded upstream answer was applied.

Uncertainties

• Company search GA timing: Company search is behind an Eppo flag (EnableDecoupledMcpToolsChatgpt, default off for ChatGPT) with GA targeted for July 21. A beta note has been added to the doc: "Company search is currently rolling out — contact support to enable if it's not yet available in your workspace." The local "Can I search for companies?" FAQ answer already confirms company search works (from a prior enrichment) without beta framing — a reviewer may want to align that FAQ answer's framing with this new note once GA ships.
• "Do I need a paid ChatGPT plan?" expansion: Clay's code doesn't gate on ChatGPT plan type, so the claim is correct from Clay's side. Whether OpenAI restricts MCP connectors to paid ChatGPT plans is an OpenAI platform policy question not verifiable from Clay's codebase. The verifier returned UNKNOWN on this dimension. The upstream docs assert this confidently; applied as-is with this caveat noted.

Related observations

• Upstream removed the "Draft personalized outbound" note about email copy being automatically filled with Clay workspace context. Local retains this — it's useful customer information and its removal from upstream may have been accidental or a simplification choice. A human reviewer should decide whether to keep or remove it.
• Upstream's "If I send outreach from ChatGPT..." FAQ was simplified from the detailed explanation (default no Sequencer access, create a function) to a shorter "It depends on how the function is set up." Local retains the more detailed version as it provides actionable guidance.
• Once company search is fully GA (July 21), the beta note in "Find and enrich people" and the "Can I search for companies?" FAQ answer should both be reviewed for consistency.

Closes DOC-1111

[linear-code]

DOC-1111