Automations

Kyno automations are one-shot container jobs. They start for an event, do their work, and exit.

An automation is not an always-on worker or HTTP app. Do not use it for polling loops, provider subscriptions, or multi-step workflow engines.

Deploy an automation

Ask your agent:

Deploy this script as a Kyno automation that runs every hour. Pass credentials as write-only secrets.

The agent uses deploy_automation_files with one to ten triggers.

Supported triggers

Trigger	Configuration
Manual	{ "type": "manual" }
Interval	{ "type": "interval", "interval_seconds": 3600 }
Cron	{ "type": "cron", "cron": "0 9 * * 1-5" }
Webhook	{ "type": "webhook" }
Lifecycle	{ "type": "lifecycle", "events": ["deploy.ready", "deploy.failed"] }

Intervals must be between 60 and 86,400 seconds. Cron expressions have five fields and run in UTC. Lifecycle triggers accept only deploy.ready and deploy.failed.

Event data

The job may read its trigger payload from:

/run/smol/event.json

For a manual run, an agent can pass an event object to run_automation.

Webhook deployments return a webhook URL and signing secret. The receiver checks the signature and timestamp before queuing the run. Keep that signing secret private.

Runtime

An automation has five minutes to finish by default and can run for at most one hour. A failed automation run is attempted up to three times with a short delay.