Configure Windmill trigger YAML files for email, webhook, Kafka, and Postgres events.
npx skills add https://github.com/kma-core/windmill --skill triggers-kma-core
Please help me install this Agent Skill. Skill: triggers Source: https://github.com/kma-core/windmill/tree/main/system_prompts/auto-generated/skills/triggers Command: npx skills add https://github.com/kma-core/windmill --skill triggers-kma-core
{path}.{trigger_type}_trigger.yaml naming pattern for HTTP, Kafka, Postgres CDC, and email triggers. - Email Trigger Configuration: Covers local-part reservation, workspace namespacing, +key=value extra arguments, and preprocessor event wrapping. - Attachment & Payload Handling: Explains how binary attachments and large raw emails are stored as S3 objects and read via the wmill SDK. - Use Case: Route inbound order emails to a flow by creating f/inbound/orders.email_trigger.yaml, then parse attachments in the script with wmill.load_s3_file. ## Quick Start Create an email trigger configuration file for my Windmill workspace that routes incoming order emails to my processing flow.High-intent search queries and answers about installing and using this skill.
Create a file named `{path}.email_trigger.yaml` in your workspace, such as `f/inbound/orders.email_trigger.yaml`. Emails sent to the configured local-part at your Windmill email domain are routed to the linked script or flow.
Attachments arrive as S3 objects in `parsed_email.attachments[i].body`. Use `wmill.loadS3File()` in TypeScript or `wmill.load_s3_file()` in Python to fetch the bytes from the workspace S3 bucket.
Trigger files follow the pattern `{path}.{trigger_type}_trigger.yaml`, for example `u/user/webhook.http_trigger.yaml` or `f/data/kafka_consumer.kafka_trigger.yaml`. The trigger type segment determines the trigger kind.
When the workspace has no S3 resource configured, attachment bodies fall back to a placeholder string. Configure object storage in Workspace Settings, and note the server must be built with the parquet feature.
Run `wmill sync push` to push local trigger configuration files to your Windmill instance, and `wmill sync pull` to retrieve existing triggers. These commands are run manually by the user after writing the files.
adamkingsburyRoute external events to Windmill scripts and flows via YAML trigger configurations.
vpzed-devReference Windmill CLI commands for managing scripts, flows, apps, jobs, and workspace resources.
Arupbiswas09Store and retrieve large immutable objects in S3-compatible blob storage.
vpzed-devConfigure Windmill cron schedules using schedule.yaml files and wmill CLI commands.