Skip to main content
Human guide: work with your agent → Inspect one ZoomInfo action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use the five search actions to discover candidate records. Use zoominfo_lookup to resolve documented filter values before building searches. Send the JSON:API envelope exactly as documented:
Search results preserve the provider’s data, meta, and links under the Deepline result envelope. Read rows from result.data.data, pagination metadata from result.data.meta, and pagination links from result.data.links. Do not unwrap or discard pagination metadata. Deepline charges no credits for ZoomInfo enrichment actions. Do not use customer credentials for testing. rely on the provider-owned OpenAPI examples unless an explicit Deepline internal/test Partner App is available. ZoomInfo tool results retain the provider response in toolResponse.rawV2, including array-valued response fields such as company and familyTree. The company_name convenience getter uses the first provider-reported company name. inspect the observed response and read the full array when you need every associated company or family-tree entry.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.