mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-01-09 08:08:32 +00:00
25c0c030ce
Some checks failed
CodeQL Advanced / Analyze (actions) (push) Has been cancelled
CodeQL Advanced / Analyze (python) (push) Has been cancelled
Check Documentation Broken Links / Check broken links (push) Has been cancelled
Notify Downstream / notify-downstream (push) Has been cancelled
Mark stale issues and pull requests / stale (push) Has been cancelled
* adjust aop to amp docs lang * whoop no print
70 lines
2.3 KiB
Plaintext
70 lines
2.3 KiB
Plaintext
---
|
|
title: "Outlook Trigger"
|
|
description: "Launch automations from Outlook emails and calendar updates"
|
|
icon: "microsoft"
|
|
mode: "wide"
|
|
---
|
|
|
|
## Overview
|
|
|
|
Automate responses when Outlook delivers a new message or when an event is removed from the calendar. Teams commonly route escalations, file tickets, or alert attendees of cancellations.
|
|
|
|
<Tip>
|
|
Connect Outlook in **Tools & Integrations** and ensure the trigger is enabled
|
|
for your deployment.
|
|
</Tip>
|
|
|
|
## Enabling the Outlook Trigger
|
|
|
|
1. Open your deployment in CrewAI AMP
|
|
2. Go to the **Triggers** tab
|
|
3. Locate **Outlook** and switch the toggle to enable
|
|
|
|
<Frame caption="Microsoft Outlook trigger connection">
|
|
<img
|
|
src="/images/enterprise/outlook-trigger.png"
|
|
alt="Enable or disable triggers with toggle"
|
|
/>
|
|
</Frame>
|
|
|
|
## Example: Summarize a new email
|
|
|
|
```python
|
|
from outlook_message_crew import OutlookMessageTrigger
|
|
|
|
crew = OutlookMessageTrigger().crew()
|
|
crew.kickoff({
|
|
"crewai_trigger_payload": outlook_payload,
|
|
})
|
|
```
|
|
|
|
The crew extracts sender details, subject, body preview, and attachments before generating a structured response.
|
|
|
|
## Testing Locally
|
|
|
|
Test your Outlook trigger integration locally using the CrewAI CLI:
|
|
|
|
```bash
|
|
# View all available triggers
|
|
crewai triggers list
|
|
|
|
# Simulate an Outlook trigger with realistic payload
|
|
crewai triggers run microsoft_outlook/email_received
|
|
```
|
|
|
|
The `crewai triggers run` command will execute your crew with a complete Outlook payload, allowing you to test your parsing logic before deployment.
|
|
|
|
<Warning>
|
|
Use `crewai triggers run microsoft_outlook/email_received` (not `crewai run`)
|
|
to simulate trigger execution during development. After deployment, your crew
|
|
will automatically receive the trigger payload.
|
|
</Warning>
|
|
|
|
## Troubleshooting
|
|
|
|
- Verify the Outlook connector is still authorized; the subscription must be renewed periodically
|
|
- Test locally with `crewai triggers run microsoft_outlook/email_received` to see the exact payload structure
|
|
- If attachments are missing, confirm the webhook subscription includes the `includeResourceData` flag
|
|
- Review execution logs when events fail to match—cancellation payloads lack attendee lists by design and the crew should account for that
|
|
- Remember: use `crewai triggers run` (not `crewai run`) to simulate trigger execution
|