Event-driven workflow triggering with real-time processing and AI-powered filtering

Integration Trigger

The Integration trigger enables event-driven workflow execution by responding to events from connected services and applications. It provides real-time processing with intelligent filtering capabilities to ensure workflows are triggered only when relevant events occur.

Configuration

Input Schema

Field	Type	Required	Description
`integrationId`	`string`	Yes	ID of the connected integration service
`eventTypes`	`string[]`	No	Specific event types to listen for
`filterPrompt`	`string`	No	AI-powered filtering criteria

Basic Configuration

triggers:
  github_pr_trigger:
    type: "integration"
    input:
      integrationId: "github_main_repo"
      eventTypes: ["pull_request.opened", "pull_request.synchronized"]
    filterPrompt: "Only trigger for pull requests targeting the main branch"

Event Context

Integration triggers provide rich context about the triggering event:

Common Context Variables

# Available for all integration triggers
- "{{ trigger.integrationId }}"     # Source integration
- "{{ trigger.eventType }}"         # Specific event type
- "{{ trigger.originalPayload }}"   # Raw event data
- "{{ trigger.filteredPayload }}"   # Processed event data
- "{{ trigger.source }}"            # Event source system
- "{{ trigger.timestamp }}"         # When event occurred

Service-Specific Context

- "{{ trigger.repository }}"        # Repository information
- "{{ trigger.pullRequest }}"       # PR details (if applicable)
- "{{ trigger.author }}"            # Event author
- "{{ trigger.changes }}"           # Files changed
- "{{ trigger.labels }}"            # Associated labels

- "{{ trigger.channel }}"           # Channel information
- "{{ trigger.user }}"              # Message author
- "{{ trigger.message }}"           # Message content
- "{{ trigger.thread }}"            # Thread context
- "{{ trigger.mentions }}"          # User mentions

- "{{ trigger.table }}"             # Affected table
- "{{ trigger.operation }}"         # CRUD operation
- "{{ trigger.record }}"            # Record data
- "{{ trigger.changes }}"           # Changed fields
- "{{ trigger.metadata }}"          # Transaction metadata

AI-Powered Filtering

Smart Event Filtering

Integration triggers use AI to intelligently filter events based on natural language criteria:

# Complex filtering with natural language
triggers:
  smart_pr_review:
    type: "integration"
    input:
      integrationId: "github_repo"
    filterPrompt: |
      Trigger for pull requests that:
      - Have more than 100 lines of code changes
      - Modify files in the /src directory
      - Are not from dependabot
      - Target the main or develop branch
      - Include tests or documentation updates

Content-Based Filtering

# Filter based on content analysis
triggers:
  content_moderation:
    type: "integration"
    input:
      integrationId: "social_platform"
    filterPrompt: |
      Trigger for posts that may need moderation:
      - Contain potentially offensive language
      - Have been reported by multiple users
      - Include suspicious links or attachments
      - Are from new accounts with no verification

Business Logic Filtering

# Business rule-based filtering
triggers:
  high_value_customer:
    type: "integration"
    input:
      integrationId: "crm_system"
    filterPrompt: |
      Trigger for customer interactions where:
      - Customer lifetime value > $10,000
      - Account status is 'premium' or 'enterprise'
      - Previous support tickets were escalated
      - Contact method preference is 'phone' or 'priority email'

Use Cases

Automated Code Review

# AI-powered code review triggering
triggers:
  code_review_trigger:
    type: "integration"
    input:
      integrationId: "github_main"
    filterPrompt: |
      Trigger automated review for pull requests that:
      - Modify critical system files (auth, payment, security)
      - Have more than 200 lines of changes
      - Are from external contributors
      - Touch database migration files

Customer Support Automation

# Intelligent support ticket routing
triggers:
  support_ticket_router:
    type: "integration"
    input:
      integrationId: "zendesk_integration"
    filterPrompt: |
      Route urgent tickets that:
      - Contain keywords like 'down', 'broken', 'critical', 'urgent'
      - Are from enterprise customers
      - Relate to payment or billing issues
      - Were submitted outside business hours

Security Incident Response

# Security event monitoring
triggers:
  security_incident:
    type: "integration"
    input:
      integrationId: "security_logs"
    filterPrompt: |
      Trigger security response for events indicating:
      - Multiple failed login attempts from same IP
      - Access attempts to restricted resources
      - Unusual data download patterns
      - Login from unexpected geographic locations

Content Management

# Social media content monitoring
triggers:
  content_monitor:
    type: "integration"
    input:
      integrationId: "social_platform"
    filterPrompt: |
      Monitor content that may need attention:
      - Posts with high engagement but negative sentiment
      - Content flagged by community moderators
      - Brand mentions with complaint keywords
      - Viral content requiring quick response

Data Pipeline Triggers

# Data processing pipeline
triggers:
  data_pipeline:
    type: "integration"
    input:
      integrationId: "data_warehouse"
    filterPrompt: |
      Start data processing when:
      - New data files are uploaded to staging
      - Files are larger than 100MB
      - Data contains customer transaction records
      - Upload occurs during processing windows

Advanced Patterns

Multi-Integration Orchestration

Coordinate events from multiple services to create sophisticated automation workflows:

# Coordinate events from multiple services
triggers:
  deployment_trigger:
    type: "integration"
    input:
      integrationId: "github_repo"
    filterPrompt: "Release tagged and CI tests passed"
    
  notification_trigger:
    type: "integration"
    input:
      integrationId: "slack_devops"
    filterPrompt: "Deployment started or completed messages"
    
  monitoring_trigger:
    type: "integration"
    input:
      integrationId: "monitoring_system"
    filterPrompt: "Performance alerts after deployment"

Context-Aware Filtering

Create intelligent filters that consider business context, time zones, and operational requirements:

# Business hours and user context
triggers:
  business_hours_support:
    type: "integration"
    input:
      integrationId: "customer_portal"
    filterPrompt: |
      During business hours (9 AM - 6 PM EST), trigger for:
      - All customer inquiries
      - Any technical issues
      - Billing questions
      
      Outside business hours, only trigger for:
      - Critical system outages
      - Enterprise customer escalations
      - Security incidents

Workflow Suspension and Resume

Resume suspended workflows based on external approval events and validation processes:

# Resume suspended workflows based on integration events
triggers:
  workflow_resume:
    type: "integration"
    input:
      integrationId: "approval_system"
    filterPrompt: |
      Resume workflows when:
      - Manager approves pending requests
      - Budget approval is granted
      - Legal review is completed
      - External validation is received

Troubleshooting

Summary

Integration triggers enable powerful, intelligent automation that responds to real-world events across your entire technology stack, making your workflows truly reactive and responsive to business needs.

Integration Trigger

Events Not Triggering

Too Many False Positives

Missing Event Context

On this page