How to choose where an agent team can be called from in GTM One
Learn how to choose the places an agent team can be started from.
Learn how to choose the places an agent team can be started from.
Overview
An agent team can be started from more than the Agent Teams page. The Entry Points card in the agent team's settings lets you choose where it can be invoked from. The card is titled "Entry Points" and reads "Choose where this Agent Team can be invoked from".
When your organization has this turned on, the card shows four entry points in two groups:
- External callers: REST API (call the agent team from your own code or automations) and MCP Server (expose it as a tool to AI clients such as Claude, ChatGPT and Cursor).
- Inside ZoomInfo: Audiences (use it in Audience builds) and Seller Tools (profile pages and other seller-facing surfaces).
An entry point your organization cannot use yet is greyed out and shows a "Coming soon" label. You cannot turn it on, and it is left out when you save. Which entry points are ready can differ from one organization to another. If you do not see the four entry points, ask your ZoomInfo admin whether this is turned on for your organization.
Before you start
- You need to be able to edit the agent team. If you can view the team but not edit it, the checkboxes are turned off. Ask a teammate with edit access to change them.
- The agent team needs a description of at most 500 characters before any entry point can be turned on. Step 3 below shows where you write it.
Turn entry points on or off
- In the left navigation panel, click Agent Teams, then open the agent team you want to change.
- Open the Settings tab and find the Entry Points card.
- Select the checkbox beside the entry point you want to allow. If the team has no description yet, the entry point stays off and the message "Add a description before turning this on." appears under it. Click Edit in Document view, write the description in the Description block (an empty one reads "Required to turn on an entry point"), then come back and select the checkbox again. A description is only asked for when you turn on an entry point that was not already saved as on.
- Clear the checkbox beside any entry point you do not want.
- Add at least one input field if you can. The card recommends one when entry points are on, so callers know what data to pass in.
- Save your changes.
If you save with an entry point on and no description, the save does not go through and a message reads "Add a description before saving with an entry point turned on, or turn the entry points off". If the description is longer than 500 characters, the save is refused with "Shorten the description to 500 characters or fewer before saving". GTM One never cuts the text short, so shorten it yourself and save again.
REST API cannot be turned off while MCP Server is on. Its row shows "Required by MCP Server", because the MCP Server is served through the REST API. Turn MCP Server off first if you want to clear REST API.
The same card appears, read only, on the agent team's inputs page, so you can see which entry points are on without changing them.
If you see an error
- "Coming soon" beside an entry point. Your organization cannot turn that entry point on yet. Contact your ZoomInfo admin or account team to ask when it is available.
- "Add a description before turning this on." The team has no description. Click Edit in Document view, add one, and turn the entry point on again.
- "Add a description before saving with an entry point turned on, or turn the entry points off" The save was stopped because an entry point is on and the description is empty. Add a description, or clear the entry points, then save again.
- "Shorten the description to 500 characters or fewer before saving" The description is too long. Shorten it and save again.
- "A description is required when any entry point is on; at least one input field is recommended." This note shows under the card while entry points are on. Add a description, and add an input field so callers know what to pass in. The agent team can still be saved without an input field.