File Event Trigger

What it does

Fires when a file matching a pattern is created, updated, or deleted in the store's managed file storage.

Configuring it

• File Events — required. Which events trigger the workflow: file created or updated, or file deleted. Defaults to created/updated. Note the underlying storage can't distinguish a brand-new file from an overwrite of an existing one — both count as "created or updated".
• File Pattern — required. The filename pattern to match, relative to the store's file storage. Supports an exact match (invoices/march.csv), :param named segments (uploads/:year/report.pdf), or * wildcards (invoices/*.csv).

Examples

Any CSV added or replaced under invoices/

{ "fileEvents": ["created_or_updated"], "filePattern": "invoices/*.csv" }

Created, updated, or deleted, matched against a named path segment

{ "fileEvents": ["created_or_updated", "deleted"], "filePattern": "uploads/:year/report.pdf" }

See also

• API Endpoint Trigger — Creates a dedicated API endpoint for synchronous workflow execution.
• GraphQL Trigger — Creates a native GraphQL endpoint with schema configuration and automatic field filtering.
• Webhook Trigger — Triggered by incoming HTTP webhook requests, with optional async execution, retry, and throttling.
• Schedule Trigger — Triggered on a scheduled basis using cron expressions.