Manual & Scheduled Triggers

Manual Trigger

Category: Manual

What it does: Runs the workflow on demand. The user (or API) supplies inputs when starting the run.

Inputs

• Custom input fields (defined when creating the automation) — You add one or more fields (text, number, date, file, dropdown, etc.). Each run supplies values for these. Common types: single-line text, multi-line text, number, date, time, file upload, single-select dropdown, multi-select.

Outputs

The trigger exposes each custom input as a variable so later steps can reference it (e.g. #trigger.customerName, #trigger.uploadedFile).

Output schema

• inputName — Value provided for each custom input field you defined. Use the variable picker in the step editor to see exact field names (e.g. #trigger.inputName).

Use cases: Testing with specific data, one-off processing, user-initiated document generation.

Scheduled Trigger

Category: Scheduled

What it does: Runs the workflow automatically on a time-based schedule.

Inputs

• Schedule — When to run. Can be a cron expression or a preset (e.g. every hour, daily, weekly, monthly).
• Timezone — Timezone used for schedule execution so “daily at 9:00” runs at 9:00 in that timezone.
• Frequency — How often: hourly (every N hours), daily (at a specific time), weekly (specific weekdays), monthly (specific day(s) of month), or custom cron for full control.

Outputs

The trigger provides the execution time and schedule metadata so you can use them in steps (e.g. in filenames or reports).

Output schema

• executionTime / timestamp — Date and time when this run was triggered (ISO or epoch, depending on product).
• schedule — Schedule configuration (frequency, timezone, next run if exposed).

Use cases: Daily reports, weekly sync, monthly billing, hourly checks.