Can't find triggers in agent overview

(0) Share

Report

Posted on by CU20051355-1

Hello,
I am creating an agent in copilot studio, that will review, correct, standardize and reply to customers email but saving the emails to supervisor email draft for the supervisor to review to review the email then respond to the client. In copilot, I have created a child agent that handles the review, correction and standardization of user's notes. Now I want to create another child agent to help with the email response. However, I am finding it difficult to achieve since I can't find triggers in the agent overview. Can anyone here help point towards the right direction and what to do?

Categories:

Autonomous agents

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

chiaraalina 2,023 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi

The event triggers that you see in the main agent's overview are only for standalone agents with generative orchestration turned on.

Child agents are invoked by parent via orchestration and have no separate trigger UI.

You're not missing a UI element. Child agents fundamentally don't support event triggers. The main agent is the entry point for all external events.

Your architecture should use a main agent with an event trigger (email arrival) that orchestrates both child agents sequentially, then calls a Power Automate action to save drafts.

1. Add Event Trigger to Main Agent

2. Create Child Agent 1 (Review & Standardization) (New child agent that Reviews, corrects, and standardizes customer notes)

3. Create Child Agent 2 (Email Draft) (New child agent that Drafts professional email replies to customers)

4. Add Power Automate Action to Main Agent

Hope it helps!

Was this reply helpful? Yes No
Suggested answer

Sayali Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello CU20051355-1,

Copilot Studio agents (including child agents) don’t have triggers like Power Automate, so you won’t find any “when email arrives” type options inside the agent. Instead, agents are invoked by a parent agent or external process. For your scenario, the correct approach is to use Power Automate as the trigger (e.g., new email), call your parent agent, and let it orchestrate both child agents—one for review/standardization and another for generating the reply. The final draft is then returned to Power Automate, which creates a supervisor review draft email.

Was this reply helpful? Yes No