Event Trigger

The Event Trigger node starts a workflow when a specific system event occurs. It's the most common trigger type, used for reactive automations that respond to meetings and other activities.

Overview

Configuration

Event Types

Output Schema

The Event Trigger outputs a trigger object:

{
  "meetingPlanId": "mp_abc123def456",
  "dealRoomId": 12345,
  "organizationId": 67890,
  "event": "MEETING_ENDED",
  "firedAt": "2024-01-15T14:30:00.000Z"
}

Examples

Basic Example: Post-Meeting Follow-up

Trigger a workflow when any meeting ends:

Configuration:

• Event: MEETING_ENDED

Usage in downstream node:

trigger.meetingPlanId  // Access the meeting ID

Advanced Example: Pre-Meeting Briefing

Generate a briefing 1 hour before meetings:

Configuration:

• Event: MEETING_START_MINUS_1H

Workflow pattern:

[Event Trigger: MEETING_START_MINUS_1H]
        │
        ▼
[Load Meeting] ──── Fetch attendees, context
        │
        ▼
[AI Agent] ──────── Research attendees, generate briefing
        │
        ▼
[Slack Post] ────── Send briefing to rep

Testing with Trigger Execution

Use the trigger execution feature to test workflows without waiting for real events:

Testing process:

1. Keep your Event Trigger set to your desired event type (e.g., MEETING_ENDED)
2. Click the Trigger button in the toolbar
3. In the trigger execution modal, fill in the form with your test data
4. Click Execute

The workflow executes with your provided data. No need to switch event types—test and release with the same configuration.

Best Practices

1. Choose the Right Event Timing

2. Handle Missing Data

Not all events have all data. For example, MEETING_START_MINUS_24H fires before the meeting has a transcript:

// Check if transcript exists before using
has(json.callRecording) && json.callRecording.transcript != ""

3. Use Deal Room Context When Needed

For deal-specific workflows, use MEETING_ENDED_FOR_DEAL_ROOM:

• Only fires for meetings associated with deal rooms
• dealRoomId is always populated
• Better for CRM update workflows

4. Development Workflow

1. During development: Use MANUAL event for quick testing
2. Before releasing: Switch to the real event type
3. After releasing: Test with a real meeting to verify

Common Issues

Workflow doesn't trigger

Symptoms: Meeting ends but workflow doesn't run

Solutions:

1. Verify workflow is Active (not Draft)
2. Check the event type matches your expectation
3. Confirm the meeting is tracked in Decision Site
4. Review execution history for errors

Wrong meeting data

Symptoms: Workflow runs but with unexpected meeting

Solutions:

1. Verify meetingPlanId is correct in trigger output
2. Check if duplicate meetings exist
3. Ensure Load Meeting node uses trigger.meetingPlanId

Multiple executions for same meeting

Symptoms: Workflow runs more than once for a meeting

Solutions:

1. Check for multiple versions of the workflow with Active status
2. Review trigger configuration for duplicates
3. The system should deduplicate—contact support if persists

Related Nodes

• Scheduled Trigger - Time-based triggers
• Load Meeting - Fetch meeting data after trigger

Technical Details

Event Generation

Events are generated by the Decision Site system:

• Meeting events come from calendar integration and recording system
• Pre-meeting events are materialized by a scheduler looking ahead
• Manual events are created when user clicks the Trigger button

Deduplication

The system prevents duplicate executions:

• Key: organizationId + workflowVersionId + meetingPlanId + event
• Same event for same meeting = single execution
• Different workflow versions = separate executions

Event Ordering

Pre-meeting events fire in sequence:

-24H → -6H → -1H → -30M → -15M → START → ENDED

Each event is independent—missing one doesn't affect others.