Overview
A trigger is the first node in every EKB workflow. Without a trigger, a workflow cannot run. Triggers determine the entry point for execution and make their output variables available to every downstream node.
note
Every workflow must begin with exactly one trigger. You cannot add more than one trigger to a single workflow.
Trigger categories
Core
General-purpose triggers for manual runs, scheduled execution, HTTP requests, and file uploads.
Communication
Triggers that fire in response to incoming emails, the end of an EKB-recorded meeting, or a Telegram bot message.
Google
Triggers that react to activity in Google Forms and Google Sheets.
All triggers at a glance
| Trigger | Category | Description |
|---|---|---|
| Manual Input | Core | Start a workflow on demand with user-defined input fields. |
| Webhook | Core | Start a workflow via an incoming HTTP request from an external system. |
| Schedule | Core | Start a workflow automatically on a recurring cron-based schedule. |
| File Upload | Core | Start a workflow when one or more files are uploaded. |
| Communication | Start a workflow when a matching email is received in Gmail or Office 365. | |
| EKB Meeting End | Communication | Start a workflow when an EKB-recorded meeting ends and notes are generated. |
| Telegram: New Message | Communication | Start a workflow when the Telegram bot receives a new message. |
| Google Forms: New Response | Start a workflow when a new response is submitted to a Google Form. | |
| Google Sheets: New Row | Start a workflow when a new row is appended to a Google Sheet. | |
| Google Sheets: New or Updated Row | Start a workflow when a row is added or modified in a Google Sheet. |