Triggers
Add, list, remove, and test flow triggers from the command line, and browse built-in trigger presets.
Triggers define when and how a flow starts: on a schedule, in response to a webhook, when a file appears, or on a platform event. The triggers and trigger preset commands manage triggers in your workspace config and interact with the running sidecar.
Listing trigger kinds
To see all supported trigger kinds and their required parameters:
Listing triggers in a config
By default this reads agentskit-os.config.yaml in the current directory. Pass a different path with --config <path>.
Adding a trigger
For example, to add a cron trigger that fires every day at 09:00:
To add an inbound webhook trigger:
Check agentskit-os triggers add --help for the full list of kind-specific flags.
Removing a trigger
Pass --config <path> to target a specific config file.
Testing a trigger
Sends a synthetic event through the sidecar to verify a trigger is wired correctly:
Viewing trigger run history
List recent executions for a trigger:
Getting the inbound URL for a webhook trigger
Prints the inbound URL that external systems should POST to.
Enabling or disabling a trigger
Trigger presets
AKOS ships curated trigger presets — ready-to-copy configurations for common scenarios. Presets are read-only reference material; use them as a starting point when adding triggers.
List presets
Output as JSON:
Show a preset
The command prints the preset's title, description, and the full trigger configuration block you can copy into your config.
Output as JSON:
Making your workspace reachable for webhooks
By default the sidecar binds its webhook listener to 127.0.0.1 (loopback only). To receive webhooks from external systems, start the sidecar with --public:
Pin the webhook port:
When --public is used, the CLI prints a security warning. Run behind a firewall or trusted tunnel and ensure every webhook trigger verifies its signature.