CrewAI Enterprise Trigger Examples

This repository contains examples of Trigger payloads to help you develop Automation Triggers check it out here. All data has been sanitized and replaced with safe, non-sensitive sample values for development and testing.

🚀 What's Included

• 📄 JSON Payload Samples: Real-world examples for each integration
• 🤖 Ready-to-Use Crew Examples: Complete CrewAI implementations for each trigger type
• 📋 Multiple Payload Variations: Different structures and use cases per integration

📁 Repository Structure

Each integration directory contains both JSON payload samples and corresponding CrewAI crew implementations:

gmail/
├── new-email-payload-1.json         # Database connection error alert
├── new-email-payload-2.json         # Performance warning alert
├── thread-updated-sample-1.json     # Deployment failure alert
├── new-email-crew.py                # General email processing crew
└── gmail-alert-crew.py              # System alert email crew

🤖 CrewAI Examples

Each integration includes ready-to-use CrewAI crew implementations that demonstrate how to process different payload types.

Example: Gmail Integration

The Gmail integration shows how different payload structures require specialized crews:

• new-email-crew.py: General email processing with header parsing and content analysis
• gmail-alert-crew.py: Specialized crew for system alerts with incident response focus

Pattern: Each crew is tailored to handle specific payload structures and business contexts within the same integration.

All other integrations follow this same pattern - they include both general-purpose crews and specialized crews for different payload types (e.g., Google Calendar has separate crews for regular events, working location events, and meetings with attendees).

🚀 Quick Start

1. Choose a crew based on your integration and payload type
2. Copy the crew file to your project
3. Replace the sample payload with your actual trigger payload
4. Run the crew:

crew = YourChosenTrigger().crew()
crewai_trigger_payload = "YOUR_ACTUAL_PAYLOAD_HERE"
result = crew.kickoff({'crewai_trigger_payload': crewai_trigger_payload})

📧 Sample Scenarios

Example: Gmail Integration

new-email-payload-1.json - Database Connection Error

• Scenario: Critical database connection pool exhaustion
• Service: AlertService from payment gateway
• Alert Level: Critical
• Environment: Production
• Crew Example: gmail-alert-crew.py
• Key Features: Complete SMTP headers, authentication results, alert details

thread-updated-sample-1.json - Deployment Failure

• Scenario: Kubernetes pod startup failure during rolling update
• Service: AlertService from API gateway
• Alert Level: Critical
• Environment: Production
• Crew Example: gmail-alert-crew.py
• Key Features: Deployment logs, rollback information, Kubernetes events

All other integrations follow this same pattern with realistic business scenarios covering different payload structures and use cases (calendar events, file operations, CRM records, etc.)