Skip to main content
Workflow Dume.ai Trigger

Using the Trigger Node

The Trigger Node starts a workflow without manual chat input. It listens for time-based schedules, external integration events, or incoming webhooks and then injects mapped data into downstream nodes.
You can define multiple trigger configurations (e.g., a daily schedule plus a webhook). Only active (enabled) triggers fire. Incoming payload fields are mapped to workflow input variables, enabling fully automated runs.
Workflow Dume.ai trigger node

Configuration Panel

The Trigger Node configuration is organized into sections:
  • Integration
  • Schedule
  • Webhook
Runs when a connected tool emits an event.
  • Source Integration: e.g. Gmail, Calendar, GitHub, Jira.
  • Event Type: email_received, new_issue, meeting_created, workflow_failed, etc.
Workflow Dume.ai trigger integration

Examples in Practice

Daily KPI Digest

  • Type: Schedule (08:00 daily)
  • Maps: kpi_revenue, kpi_churn from external analytics endpoint (via later Tool Node)
  • Flow: Trigger → Tool Node (fetch KPIs) → LLM Node (summarize) → Output

Meeting Follow-Up

  • Type: Integration Event (Calendar: meeting_created)
  • Filter: duration >= 30m AND attendee_count > 2
  • Maps: title, start_time, attendees
  • Flow: Trigger → Delay (1h) → LLM summary → Send recap

Critical Issue Escalation

  • Type: Integration Event (Jira: issue_created)
  • Filter: priority=High OR labels contains “security”
  • Maps: issue_key, summary, priority
  • Flow: Trigger → Condition (priority) → LLM (draft Slack alert) → Tool (post Slack)

Webhook: Deployment Report

  • Type: Webhook (POST from CI)
  • Payload: serviceName, version, status, metrics
  • Flow: Trigger → LLM (generate release note) → Store in Docs

GitHub PR Watcher

  • Type: Integration Event (GitHub: pull_request_opened)
  • Filter: base_branch=main AND lines_changed > 500
  • Flow: Trigger → LLM (summarize changes) → Tool (request reviewers)

Best Practices

GoalTip
Noise reductionUse filters and dedup window
ReliabilitySet retry with exponential backoff
ClarityName mapped variables consistently
SafetyStart read-only; add write nodes later
ScalingMonitor run volume; adjust caps

Troubleshooting

IssueFix
Trigger not firingConfirm enabled, time zone, cron syntax
Duplicate runsAdjust dedup window or filters
Missing payload fieldVerify mapping and incoming field name
Webhook rejectedCheck secret, content-type, schema
Excess volumeLower max runs per interval or refine filters

Sample Flow

Trigger (Calendar meeting_created, filter: internal only)
Delay 30m
LLM summarize discussion template
Tool send Slack recap
Output final summary object
Trigger Node configured. Workflow will run automatically when conditions are met.