GTM AIGTM AI
Sign up

How to Run an Agent Team Manually in GTM One

Learn how to start an agent team run yourself and review what each step returned.

Srivatsa MarthiSrivatsa MarthiPrincipal Product Manager

Learn how to start an agent team run yourself and review what each step returned.

Overview

Every new agent team begins with a manual trigger step named Run as Form. When you run a team manually, you start the run yourself from the agent team's page, choose where its inputs come from, and the team works through its steps in order. In the team's list of runs, the Trigger column shows Run as Form for a run started this way.

Whether you can run an agent team depends on your role. If the run button is unavailable, ask your ZoomInfo admin.

Run an agent team manually

  1. Open Agent Teams in GTM One, and then open the agent team you want to run.
  2. In the top-right corner of the agent team's page, click Run agent team (depending on the page and the team's trigger, the button may read Run or Run manual).
  3. If the Review before running dialog appears, click Fix Errors to go to the problem, or click Run without fixing to continue.
  4. In the Data source (optional) step of the Run Agent Team dialog, select Form input to type the inputs yourself, or select Run without inputs.
  5. If you selected Form input, enter a value for each input the form lists.
  6. Click Next.
  7. In the Run as step, select Run as Me, or select Run as Others and choose the users to run it on behalf of. The run is repeated once for each user you select, using their own data access and credits.
  8. Click Next until you reach the Review & Run step.
  9. Review the selected source and the estimated credits, and then click Confirm and Run.
  10. Open the agent team's Runs tab to follow the run's progress and review its results.

Run as Others

When you run as others, each user you select gets a separate run with their own context. Each run uses that user's data access and that user's AI action credits, not yours, so the credit estimate is counted once per user. The Review & Run step shows each user's credit status, with users who may run short listed first. The users you can choose, and how many, come from your organization's settings.

If the team sends messages or updates connected systems, every selected user's run does so, which can duplicate the outreach. When a team uses tools that would duplicate external actions, GTM One lets you pick only one user, or run it as yourself.

To run the team with the rows of an audience or a CSV file instead, select Audience or CSV in the Data source (optional) step. See How to run an agent team on an audience and How to run an agent team from a CSV file.

Review the output of a run

Each step in the team has its own output, so you can see what every step returned.

  • Step columns are headed Output: Step 1, Output: Step 2, and so on. A step inside a loop is numbered with its loop (e.g., Output: Step 2.1).
  • A conditional routing step's column (e.g., Output: Step 3 Conditional routing) shows the path the run took. In the run's own output view, a matched condition is shown as Condition 1 followed by the condition's text, and a run that matched no condition shows Default path taken - no conditions met.
  • Steps on a path the run did not take show Not run.
  • A step inside a loop produces one output for each loop item. The runs table shows the output for the first item, and the run's output view lists each item as #1, #2 and so on, followed by the item's name when it has one.
  • A step with nothing to show reads No output available.
  • If you provided a CSV file as an input, it appears as CSV file with only the file's name.

If a run is held back because the team's monthly credit budget or your organization's AI action credits are used up, the run is saved as Rejected without starting. Its status can be shown as a warning rather than an error, because it can be reinitiated once the budget or credits allow it. See Troubleshooting agent team runs blocked by credits.

Resources

An agent team open in GTM One with the Run as Form trigger at the top and the run control in the header.