# Trigger

> The event that starts an agent flow in Copilot Studio: a manual run, a recurring schedule, or something happening elsewhere, such as an incoming email or an agent's call.

**Category:** Copilot

**Every [agent flow](/glossary#agent-flow) starts with a trigger, followed by at least one action.** Three types cover almost everything. A manual (instant) trigger runs on demand, which is handy while you build and test. A scheduled trigger runs on a recurrence you set, the direct equivalent of a Claude [scheduled task](/glossary#scheduled-task). An event-based trigger fires when something else happens.

Microsoft's own example of an event-based trigger: your manager sends an email (the trigger), and Copilot posts a message in Teams (the action). One event-based trigger matters most for agents: **"When an agent calls the flow"**. It lets an agent run the flow mid-conversation as a tool and use the result in its answer. With a scheduled trigger, check the time zone and run a manual test before you rely on it.

## At work

A team sets a scheduled trigger for Monday at 8am, confirms the time zone, and runs the flow manually twice before switching it to the live schedule.

## Often confused with

A prompt. A [prompt](/glossary#prompt) is something a person types to get one answer; a trigger starts an automated flow without anyone typing, once it is set up.

## Related terms

- Agent flow
- Copilot Studio
- Scheduled task
- Autonomous agent

## See it in a lesson

[Copilot Studio: build and automate](/en/learn/copilot/advanced/copilot-studio)

## Further reading

- [Agent flows overview (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoft-copilot-studio/flows-overview): How triggers and actions fit together in an agent flow.
- [What is Copilot Studio? (Microsoft Learn)](https://learn.microsoft.com/en-us/microsoft-copilot-studio/fundamentals-what-is-copilot-studio): The bigger picture of agents and automations in Copilot Studio.

---

Last updated: 14/10/2026  
Source: Rollo Academy glossary