native-trigger

Create a SQL migration adding the service to the native_trigger_service, TRIGGER_KIND, and job_trigger_kind enums, implement the External trait in a new module under backend/windmill-native-triggers/src, register routes and sync logic, then add frontend registry entries and a Svelte form component.

The External trait defines the contract every native trigger service implements, including create, update, get, delete, exists, and maintain_triggers methods plus associated types for service config, trigger data, and OAuth data. It lives in backend/windmill-native-triggers/src/lib.rs.

OAuth tokens use a three-table pattern: workspace_integrations holds base_url and client credentials metadata, the variable table stores the encrypted access_token, and the account table stores the refresh_token. The decrypt_oauth_data() function assembles these into a unified OAuthConfig struct.

Use the short path by overriding service_config_from_create_response() to return Some(config) when the external_id is known before creation, as Google does. Use the default update+get pattern when the remote service assigns the external_id and the webhook URL must be corrected afterward, as Nextcloud does.

Services with expiring channels implement renewal logic in maintain_triggers() instead of using reconcile_with_external_state(). For example, Google Drive channels expire in 24 hours and are renewed when under one hour remains, while Calendar channels renew when under one day remains.