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.

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.

Defines time-based execution.

Frequency: once, interval (every 15m), daily, weekly, monthly.
Cron Expression (advanced): e.g. 0 8 * * 1-5 (8 AM weekdays).
Timezone: ensures consistent execution across regions.
Start / End (optional): limit active window.
Skip Holidays (optional list): provide ISO dates to skip.

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

Goal	Tip
Noise reduction	Use filters and dedup window
Reliability	Set retry with exponential backoff
Clarity	Name mapped variables consistently
Safety	Start read-only; add write nodes later
Scaling	Monitor run volume; adjust caps

Troubleshooting

Issue	Fix
Trigger not firing	Confirm enabled, time zone, cron syntax
Duplicate runs	Adjust dedup window or filters
Missing payload field	Verify mapping and incoming field name
Webhook rejected	Check secret, content-type, schema
Excess volume	Lower 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.

Overview

Ways to reach dume

Integrations

AI Tools

Workflows

Agents

Product

Use cases

Trigger Node

Using the Trigger Node

Configuration Panel

Examples in Practice

Daily KPI Digest

Meeting Follow-Up

Critical Issue Escalation

Webhook: Deployment Report

GitHub PR Watcher

Best Practices

Troubleshooting

Sample Flow

​Using the Trigger Node

​Configuration Panel

​Examples in Practice

Daily KPI Digest

Meeting Follow-Up

Critical Issue Escalation

Webhook: Deployment Report

GitHub PR Watcher

​Best Practices

​Troubleshooting

​Sample Flow

Using the Trigger Node

Configuration Panel

Examples in Practice

Best Practices

Troubleshooting

Sample Flow