How to turn on an agent team trigger with AI Builder

Learn how AI Builder asks before it switches a trigger on, and what to do when it will not.

Overview

Turning a trigger on is the one step AI Builder never takes on its own. Once a trigger is on, the agent team starts by itself and spends credits each time it runs. Saving, listing and editing a team never need a confirmation. A trigger that is not on yet never fires.

AI Builder turns a trigger on only after you say yes in the message right after it asks. A yes you gave earlier does not count.

Before you start

• Turning a trigger on needs permission to run and activate agent teams. If your role does not have it, AI Builder will not offer to turn the trigger on and does not send you elsewhere to do it. You can still build and edit. Ask your ZoomInfo admin for access.
• The team needs at least one step and at least one trigger. See How to set a trigger on an agent team with AI Builder.

Turn on a trigger

1. Set the trigger. AI Builder replies with what will fire and when, for example the cadence, the timezone and the next run times. For a webhook it tells you that anyone who sends your key to the URL can then run the team.
2. When the team is ready, AI Builder asks "Ready to activate?" and nothing else in that reply, so your answer can only mean one thing.
3. Reply "yes", "activate it" or similar. Any other reply is treated as an edit or a question, and AI Builder asks again later.
4. Read the result. For each trigger that has a rate limit, AI Builder says what the limit is and whether you or the platform set it. It offers to change the limit.

Turning on switches on every trigger on the team at once, because there is no per-trigger switch. When there is more than one, the question names each of them.

Change a trigger that is already on

A trigger that is firing keeps its old settings until you confirm a new version. Any change to it (a new schedule, a wider or narrower condition, a different rate limit) is saved, but AI Builder tells you it is not live yet and asks again before switching it on. Removing a trigger is the exception: it stops the trigger at once and needs no confirmation. After you remove every trigger, the team is still saved and you can still run it by hand.

When AI Builder says it is not ready

AI Builder does not offer to turn a trigger on when:

• The team has no steps yet. Add a step.
• The team has no trigger. Tell AI Builder when it should run.
• A trigger is missing something it needs (for example, a schedule with no timezone, or an event trigger with no condition). Answer its question or restate the trigger.
• A trigger was made in the visual builder in a kind AI Builder cannot edit. Fix or remove it in the visual builder.

Apps the team uses that are not connected do not block turning a trigger on. AI Builder lists them as a reminder, and those steps will not run until you connect them.

If you see an error

• "Agent Team monthly credit budget reached. The team's owner can raise the limit in Settings; runs resume when it is raised or the month rolls over." The team's monthly credit budget is used up, so runs are rejected. Ask the team's owner to raise the limit, or wait for the next month.

For other problems see Troubleshooting AI Builder for agent teams.