GTM.ai
Sign up
Docs menu

Troubleshooting ZoomInfo data lookups in agent team steps in GTM One

Learn why an agent team step could not get ZoomInfo data and how to fix it.

Srivatsa MarthiSrivatsa MarthiPrincipal Product Manager

Learn why an agent team step could not get ZoomInfo data and how to fix it.

Overview

When a step asks for ZoomInfo data and none comes back, the step is told to report that plainly and not to invent the missing data. The step's output then carries one of the messages below, and the run page may show a failed step with the What went wrong card. A request that finds no matches is not an error: "none" is a valid answer and the step goes on.

Before you start

  • A failed or incomplete step. Open the run and click the step. See How to view agent team runs and results in GTM One.
  • Permission to edit the team. Most fixes edit the step's instructions. If the builder's controls are turned off, ask your ZoomInfo admin.
  • Real effects. A step that failed may have done part of its work, such as records created or messages sent by other steps. Check the destination before you run again.
  • Credits. A run that fails still uses AI credits for the work it performed.

Find the cause and fix it

  1. Open the failed run and click the failed step, then read its output and the What went wrong card. See Troubleshooting the "What went wrong" card on a failed agent team run in GTM One.
  2. Find the message in the list below and follow its fix.
  3. Edit the step's instructions in the builder. See How to ask for ZoomInfo data in an agent team step in GTM One.
  4. Start a new run. See How to run an agent team manually in GTM One.

What each message means

The lookup found nothing

  • "No data returned for:" followed by your request, then "did not retrieve any data for this request from any source." The lookup ran but no source gave data. Retry with a different or more specific request, such as the company's domain, or a different source. If the step can go on without the data, a later step may still run. On the card this usually reads "Step didn't finish".
  • "No data returned for:" followed by your request, then "could not answer this request and returned no data." The lookup reported the question is not supported, or that it could not finish within its allowed attempts, or it consulted no data source. Rewrite the request to ask for something ZoomInfo data holds (companies, people, pipeline, meetings and emails, conversations), and keep it read-only. It will not create or update records.
  • "No data returned for:" followed by your request, then "failed while handling this request and returned no data." This is a temporary platform failure. Run the team again.
  • "No data returned for:" followed by your request, then "returned no data for this request." The reply was empty. Try a different request.

The lookup did not run

  • "Error: query parameter is required." The step asked with an empty request. Say what to look up in the step's instructions.
  • "Error: No ZoomInfo access token found." The person the team runs as is not signed in to ZoomInfo for this lookup. Ask your ZoomInfo admin to check that person's access, then run again. For a triggered or scheduled run that person is the team's owner.
  • "Error: Failed to retrieve ZoomInfo access token." The sign-in check itself failed. Run again, and contact your ZoomInfo support contact if it repeats.

The service did not answer

  • "timed out." An error that begins "Error: Request to ZoomInfo" and ends "timed out." means the lookup took longer than five minutes. Narrow the request (one company, a shorter date range, fewer records) or split it across steps.
  • "Failed to connect" and "Unexpected error while querying". An error that begins "Error: Failed to connect to ZoomInfo" or "Error: Unexpected error while querying ZoomInfo" means the service could not be reached or failed unexpectedly. Wait a few minutes and run again. A temporary connection failure is retried once automatically. On the card this reads "A service didn't respond".
  • "returned status code" followed by a number. The number says why: 400 or 422, the request was rejected, so edit the step's instructions (the card reads "Input rejected"); 401 or 403, the access was refused, so ask your ZoomInfo admin; 404, nothing was found; 429, too many requests, so wait and run again; 500 or above, a service problem, so wait and run again.

If you see an error

  • "No data returned for:" The lookup got no data. Rewrite the request more specifically, or use another source, then run again.
  • "timed out." The request took over five minutes. Narrow it or split it.
  • "Error: No ZoomInfo access token found." The team's runner is not signed in to ZoomInfo. Ask your ZoomInfo admin.

If the message repeats after the fix, copy the run link and the step's Show technical detail text and click Help me optimize, or contact your ZoomInfo support contact.

Resources