How to set a trigger on an agent team with AI Builder

Learn how to ask AI Builder to start an agent team on a schedule, an event or a webhook call.

Overview

A trigger starts an agent team without you. AI Builder can set a schedule, a ZoomInfo event, an Audience row event or a webhook on a team you are building or editing.

Setting a trigger saves it on the team, and you can see it in the visual builder. It is switched off and cannot fire until you turn it on. AI Builder describes it that way: set, but not running yet. To switch it on, see How to turn on an agent team trigger with AI Builder.

A team can have several triggers. It runs whenever any one of them fires, and a condition on one trigger never limits another.

Before you start

• Open AI Builder on the team you want to change. See How to build an agent team by describing it to AI Builder.
• Setting a trigger needs permission to create and edit agent teams. Turning it on needs a different permission. Whether you have each depends on your role; ask your ZoomInfo admin.

Set a trigger

1. Open AI Builder and describe when the team should run, e.g., "every weekday at 9am Pacific" or "when a deal is marked Closed Won".
2. Answer any question it asks. For a schedule with no timezone, it asks which timezone to use; it does not guess. A timezone you name with the time ("9am Pacific") counts as your answer.
3. Read the confirmation. It says the trigger is set and not running yet. For a schedule it reads back the cadence, the timezone and the next run times, so you can catch a wrong day or coast.
4. To change the trigger, say what to change. A change to a trigger that is not firing yet is made right away. Removing one trigger, or all of them, also needs no confirmation.

Kinds of trigger

• Recurring schedule. A cadence such as weekdays at 9:00 AM. You can give a start date.
• One-time schedule. A single run at a date and time. AI Builder works out relative dates ("next Monday") from the current date and time.
• ZoomInfo event. A data change, such as a CRM record or a signal. AI Builder only uses events your account offers and reads the event's fields before writing a condition. For a condition on a picklist field, it looks up the values your account actually uses and writes one exactly as spelled. If it cannot find the value you typed in recent data, it uses "contains" and says the value has not been seen.
• State or change. "Stage is Closed Won" checks the current state. "Stage changes to Closed Won" watches for the change, and it works for one field at a time. Events that are single occurrences, such as website visits, meetings and emails, cannot detect a change; AI Builder says so and offers a CRM record event instead.
• Audience row event. Fires when a row is added to, changed in or removed from one Audience. For a changed row, it needs the one column to watch, and it lists the columns by name for you to pick. Each run gets that one row's columns. Added or updated is two triggers on one team.
• Webhook. Lets another system start the team by sending a request to a URL. See below.

Limit a trigger to an Audience

You can limit a ZoomInfo event on accounts, website visits, funding, meetings or email to companies in one Audience.

1. Open the Audience's sheet and copy the link from your browser's address bar.
2. Paste the link into AI Builder. It reads the Audience's id from the link. In a GTM Studio link, the id is the part after sheets, not the folder before it.

AI Builder needs the link or id. A name alone is not enough, and it will ask for the link. These requests are not supported, and AI Builder says so instead of setting something different:

• People or contacts in an Audience. The condition is about the company, so AI Builder offers the company version and sets it only after you say yes. A run each time a person is added to an Audience is possible as an Audience row event.
• Companies that are not in an Audience.
• Companies that must be in two Audiences at once. "In A or B" is supported, as one trigger per Audience; a company in both starts two runs for one event.
• Contact and opportunity events, which cannot be filtered by Audience.

Other conditions AI Builder cannot set

• Owner-based conditions ("my deals", "owned by me") cannot be set from chat. AI Builder offers to match the owner's email address instead, or tells you to set the owner condition in the visual builder.
• Custom CRM fields cannot be used as trigger conditions from chat.
• A trigger's kind cannot change from chat except between recurring and one-time schedules. To switch kinds, AI Builder adds the new trigger and removes the old one, and tells you the trigger was replaced and is off until you turn it on.

Webhook triggers

1. Ask AI Builder to start the team from a webhook.
2. In its reply, copy the URL and the key straight away. The key is shown once and never repeated, even if you ask later.
3. Have the calling system send the key in the X-AgentTeams-Key header. The URL refuses calls until you turn the webhook on.
4. If you lose the key, ask for a new webhook. AI Builder removes the old one and adds a new one with a new URL and key. It asks first, because systems still using the old URL stop working.

A team has at most one webhook. A webhook is always rate limited, so not every call runs the team. The reply states the limit.

Limit how often a trigger fires

ZoomInfo event triggers and webhooks are rate limited whether or not you ask. If you set no limit, the platform applies its own, and AI Builder tells you that a default applies and states the exact limit once the trigger is on. It never describes such a trigger as firing on every event.

To set your own, say so in words, e.g., "at most once an hour" or "once a day per company". A limit with no scope is one fire across all records, not one per record. AI Builder says which one it set. A schedule is not rate limited, because it already runs as often as its cadence says; to run less often, change the schedule. See How to limit how often an agent team trigger runs in GTM One.

If the trigger did not save

If AI Builder says the trigger did not land, the steps were saved but the trigger was not. Ask it to try again. See Troubleshooting AI Builder for agent teams.

For more on triggers outside AI Builder, see How to Schedule or Trigger an Agent Team in GTM One and How to trigger an agent team when an Audience changes.