Connector Triggers
Connector Triggers start a configured workflow when selected events arrive in Teams, Outlook, GitHub, or Azure DevOps. Send a new message, email, issue, or work item to a sub-agent that can triage it, summarize it, or guide the next step using its configured capabilities.
Use a Connector Trigger when the event already arrives in a connected service. For a webhook that another system calls directly, use an HTTP trigger. For work that runs on a schedule, use a scheduled task.
Supported events
| Service | Event and scope | Default conversation grouping |
|---|---|---|
| Microsoft Teams | New messages in a selected channel or group chat | One conversation per channel root message and its replies, or per group chat |
| Outlook | New email in a selected folder | One conversation per email event |
| GitHub | Newly opened issues in a selected repository | One conversation per issue |
| Azure DevOps | Newly created work items in a selected project and exact area path | One conversation per work item |
New Teams channel triggers process all messages by default. You can require a mention of the connection account and optionally include all root messages. Group-chat messages always require a verified mention of the connected account. The agent receives the triggering message content automatically, not the prior conversation history.
GitHub triggers use indexed repositories on GitHub.com or GitHub Enterprise Cloud. They exclude pull requests and only process issues from repository owners, organization members, or repository collaborators. Azure DevOps triggers only process work items created in the configured project and exact area path, not items moved there later. GitHub and Azure DevOps triggers start with new items after activation; they do not backfill earlier items.
Before you begin
- Create the sub-agent that handles the event. Give it only the tools and permissions needed for the workflow.
- For Outlook or Teams, create an authenticated connection under Builder → Connectors. The connected account must be able to access the selected folder, channel, or chat. See the Outlook and Teams setup guides.
- For GitHub or Azure DevOps, add an authorized repository under Builder → Code access. The Azure DevOps project list comes from indexed repositories. See Connect source code.
A trigger does not grant new source access or change the sub-agent's permissions. People who can post in a watched Teams conversation or create a work item in the selected Azure DevOps area can start the sub-agent. Configure the scope and tools accordingly. Event content is untrusted input.
Create a Connector Trigger
- In your agent, open Automation.
- Select Create, then Connector trigger.
- Choose an event: Respond to new email, Respond to new Teams message, Respond to new GitHub issue, or Respond to new Azure DevOps work item.
- Enter a name and display name. Select the connection or repository and the target sub-agent.
- Choose the event scope: an Outlook folder, Teams channel or group chat, GitHub repository, or Azure DevOps project and area path. An Azure DevOps area path must start with the selected project name and match the work item's area path exactly.
- Review any source-specific options, including Teams mention filters or the polling interval for GitHub and Azure DevOps. Where available, choose Thread grouping. Teams uses its conversation grouping without a grouping control in the form.
- Review the configuration and save the trigger.
Start with a focused scope, such as a dedicated inbox folder or a single team channel. Review the resulting conversations and adjust the scope and sub-agent permissions to fit your team.
Review and manage triggers
Open Automation and select a connector trigger to view its configuration and associated threads. You can edit, turn off, or delete a trigger from the automation experience. The selected event and target sub-agent cannot be changed; delete and recreate the trigger to change them. Deleting a trigger can discard queued events.
Events that arrive while a GitHub or Azure DevOps trigger is disabled are skipped. Previously accepted work can continue after a trigger is disabled or deleted.
Delivery is at least once. A retried event can run more than once, so design downstream actions to tolerate duplicates. An accepted event does not mean the agent has completed its work or sent a response. Posting back to a watched Teams conversation can cause repeated runs; limit posting tools and permissions as needed.
Troubleshooting
| Symptom | Check |
|---|---|
| No matching connection or repository appears | Add an Outlook or Teams connection under Builder → Connectors, or index an authorized repository under Builder → Code access. |
| No sub-agent appears | Create one under Builder → Sub-agents. |
| A Teams message does not start a run | Check the selected conversation and mention settings. Group chats require a verified mention of the signed-in connection account. |
| A GitHub issue or Azure DevOps work item does not start a run | Check the configured source, authorization, event eligibility, and whether the item was created after activation. |