Run Automation rule
Manually run an Automation rule immediately, outside its schedule.
Restrictions
Usage
- Rate-limited to at most once per minute per rule; a second call within that window returns
429withcode: "RequestTooFrequently". - Only enabled rules can run manually; a disabled or misconfigured rule fails preflight with a
400error before any run is created. - The call returns once the underlying agent session starts, not once the run finishes; the run continues asynchronously — use List Automation runs to check completion status.
trigger_kindis alwaysmanualfor runs started this way, distinguishing them fromschedule,http_post, andoncall_incidentruns in run history.- Every call is recorded in the account audit log.
Authorizations
App key issued from the Flashduty console. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
Rule ID.
Response
Success
Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
Result of manually running an Automation rule outside its schedule.