Kanorio

Cloud infrastructure

Automation

Owner-built automations on triggers, with conditions, branches, delays, retries, custom triggers and HTTP actions.

Available

Automations run steps when something happens: an order is paid, a form is submitted, a date arrives, or your own system reports an event. Sending an email is one action among many.

Core objects

  • Triggers and actions. A catalog with a JSON schema for each trigger's data and each action's input.
  • Automations. Conditions, branches, delays and rate limits, built in the dashboard or through the API.
  • Runs. Each execution, step by step, with retries, failure details and the option to run again.
  • Custom triggers. Report your own events with POST /sites/{id}/automations/events to start automations.

How the APIs fit

  • Read the catalog, create and edit automations, test them, and read and retry runs with the Management API.
  • The automations.run.failed webhook tells you when a run fails.

What the APIs expose

  • Automation engine: trigger/action catalog, owner-built flows, per-step runs, custom triggersAvailable
    API
    Management API (REST/MCP) automations.catalog.get, automations.templates.list, automations.flows.* (list/get/validate/create/update/set_status/archive/delete/test), automations.runs.* (list/get/rerun), automations.events.report/cancel, automations.triggers.*, automations.secrets.*; preinstalled toggles via automations.list/set_action_enabled; signed inbound endpoint POST /api/webhooks/automations/<token> (Standard Webhooks)
    Hosted site
    /automations, /automations/settings
    Webhooks
    Every trigger in the catalog is also a subscribable webhook event; custom triggers accept signed inbound webhooks (planned)

API reference

Webhook events

  • automations.run.failed · Fired when a run of an owner-built automation ends in FAILED after retries (compensation already applied). Not fired for test runs or platform-default automations; at most once per automation revision every 30 days.
  • automations.flow.paused · Fired when Kanorio turns an owner-built automation off automatically because its current revision ran more than 20 times in the past 7 days and 95% or more of those runs failed.