Keep an AI Agent Running After the Person Who Built It Leaves
Before the person who built your AI agent leaves Gumloop, make a list of what they run and who recreates each trigger.
Make a list of what the person runs while they're still there, because their triggers run on their connected accounts and stop when they lose access. Name a second Owner, have that Owner recreate each trigger, and check the Triggers tab and the Failed filter before anyone is removed.
A trigger runs on the connected accounts of the person who created it and stops when that person loses access.
What happens to the AI agent and its triggers when the builder is removed?
Their AI agents aren't deleted, but anything tied to their account can stop. Removing someone from the organization pauses their AI agent triggers and deletes their workflow triggers. At least one other user needs Owner access, since Owners can edit the AI agent, manage access, and view and manage team triggers.
Moving an AI agent to another team keeps a trigger only if its creator still has access to it in the new team. Gumloop deletes some, and restoring access afterwards doesn't bring them back.
Checked on 2026-11-10 against Gumloop's help page on keeping AI agents running when someone leaves and its page on why a trigger turns off.
What do you send Gumball, and what does the list hold?
The help page suggests asking the analytics AI agent in Gumball for a list. Its wording says "I created", so it lists what the sender created. If the person leaving built the AI agents, they send it from their own Gumball and paste you the reply.
The help page's version leaves out the word AI, and the block adds it. The page doesn't say where in Gumball the analytics AI agent sits, so send it in Gumball's chat. If the reply is thin, step 02 builds the same list by hand.
Message to send in Gumball: List the AI agents, triggers, and skills I created. For each trigger, give the AI agent it belongs to, when it runs and what its prompt asks for. Where you can't see something, write "not shown" and don't guess. List of what the person runs, one row for each trigger: AI agent | Trigger | What it does | Who created it | Who recreates it | Date recreated | Check passed [NAME OF AI AGENT] | [NAME OF TRIGGER] | [WHAT THE PROMPT ASKS FOR] | [NAME OF PERSON LEAVING] | [NAME OF NEW OWNER] | [DATE] | [YES OR NO] Before a row is marked done, any AI agent in [NAME OF PERSON LEAVING]'s personal space has been moved to a team with its skills.
How do you hand the AI agent off before anyone is removed?
- 01
Send the message and set the reply beside the AI agent builder page.
Open Gumloop, start a chat with Gumball and send the first paragraph of the block. Compare it with your own list of AI agents, Personal and each team, and add any it didn't list. Checked on 2026-11-11 against Gumloop's help page on keeping AI agents running when someone leaves and its page on Gumball.
- 02
Open each trigger and fill in what it does and who created it.
Go to the Triggers tab of every AI agent on the list. Owners see team triggers there with their schedules and prompts: your own sit under Mine, and other people's under Team. Click a trigger to open Trigger Details, whose header names the creator, and copy what the prompt asks for into the "What it does" column. Checked on 2026-11-11 against Gumloop's help page on keeping AI agents running, Gumloop's page on AI agent triggers and its help page on who can manage triggers.
- 03
Add a second Owner.
Open the AI agent's Access tab, type an email in Add an owner under Owners and click Add. How Do I Share an AI Agent With a Coworker in Gumloop? covers what each role can do. Checked on 2026-11-11 against Gumloop's help page on keeping AI agents running and Gumloop's page on AI agent access.
- 04
Have the new Owner recreate each trigger.
Write the Owner's name in the Who recreates it column. That Owner recreates each trigger from the Triggers tab, or asks the AI agent in chat to set it up, since an AI agent manages only the triggers of the person talking to it. The help page names another route for an AI agent that should always use a shared account: credentials owned by the AI agent, or a team connector. Recreating under the new Owner is the help page's route, and it's the one that runs the trigger on the new Owner's accounts. Checked on 2026-11-10 against Gumloop's help page on keeping AI agents running when someone leaves.
- 05
Check the recreated triggers before you remove the person.
Open each new trigger, click View all under Recent tasks and choose the Failed filter in Task history. Confirm the new Owner can reach everything the row names, then write yes in the last column. Don't remove the person until every row says yes, then use Organization, Members. If they still own resources, the Member removed message offers Transfer their resources. See Where Do You Find Out an AI Agent's Run Failed or Stopped? for the reasons a run stops. Checked on 2026-11-11 against Gumloop's help page on keeping AI agents running when someone leaves and its page on AI agent triggers.
I am an ambassador for Gumloop. Code VIBE20 takes 20% off your first month.
Is any trigger on the list still running on the old person's accounts?
Trigger Details names the creator. A row marked passed whose trigger still names the person leaving wasn't recreated, and it stops on removal.
After the removal, open the Triggers page in the left sidebar, set Status to Off and open each trigger to see the reason beside Off, if Gumloop shows one. Its creator was removed is a reason on Gumloop's page on why a trigger turns off, and it shouldn't be the reason for a row you marked passed.
For someone who's already left, an organization admin can still claim ownership of the AI agent. Claiming it doesn't restore the previous owner's triggers, so the admin transfers them from the Former members tab or recreates them under another user. Send the new Owner to How Often Should You Review an AI Agent's Instructions? for the instructions they'll inherit. Checked on 2026-11-11 against Gumloop's page on AI agent triggers, its page on why a trigger turns off and its help page on keeping AI agents running.
Frequently asked questions
Can an admin transfer the triggers instead of recreating them?
After you remove the member, an admin can transfer their triggers from the Former members tab, and the Member removed message offers Transfer their resources. Before the removal, the help page's route is to have the new Owner recreate them.
What if the person has already left?
An organization admin can open the AI agent, choose Claim Ownership from the ⋮ menu beside its name, and take control.
Do triggers keep running when I move the AI agent to a team?
Only the ones whose creator still has access to it in the new team, and Gumloop deletes some, including triggers that use the old team's connector. If a move would remove someone's access, add them to the new team or to the AI agent by email first.