What problem does it solve?
Adding a new native trigger integration to Windmill requires coordinated changes across database migrations, Rust backend crates, OAuth token storage, and multiple Svelte frontend components, which is error-prone without a complete map of every touchpoint.
Core Features & Use Cases
- End-to-End Implementation Guide: Walks through all 18 steps from SQL enum migrations and the
External trait implementation to frontend registries, icons, and OpenAPI regeneration.
- Architectural Patterns: Documents the two create lifecycles (short Google pattern vs. long Nextcloud update+get pattern), the three-table OAuth token storage model, and background sync strategies (reconciliation vs. channel renewal).
- Use Case: When adding a new webhook-based integration like a file storage or calendar service, follow the guide to implement the Rust service module in
windmill-native-triggers, wire up routes and sync logic, and register the trigger form, icon, and sidebar visibility in the frontend.
Quick Start
Use the native-trigger skill to add a new native trigger service integration to Windmill covering the backend crate, database migration, and frontend components.