Create Automation rule
Create an Automation rule with schedule, HTTP POST, and On-call incident triggers.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Valid app_key; management operations require the caller to manage the target rule |
Usage
- A caller may create personal rules and rules for any team in the current account;
team_idis immutable after creation. - List visibility follows session-list visibility: owners/admins see all rules; ordinary members see rules they created and rules for their teams.
http_post_tokenis returned only when creating or rotating the token. Save it immediately.- To trigger from On-call incidents, send
oncall_incident_trigger_enabled,oncall_incident_channel_ids, andoncall_incident_severities; matching events run withtrigger_kind=oncall_incident.
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
Create an Automation rule.
Rule name.
1 - 255Run cadence. Supports 4 fields (hour day month weekday, minute defaults to 0) and 5 fields (minute hour day month weekday). The minute must be one fixed integer; 6-field seconds are not supported. The create API currently requires this field even for HTTP-POST-only rules; send a valid cron and set schedule_trigger_enabled=false.
"15 9 * * *"
Task prompt sent to the AI SRE agent on each run.
1Scope team ID. 0 or omitted means a personal rule; >0 means a team in the account. Immutable after creation.
x >= 0Whether the rule is enabled after creation. Omitted API value is false; Chat/CLI create sends true by default unless the user asks for disabled.
Whether the schedule trigger is enabled. Defaults to true when omitted; HTTP-POST-only rules should send false.
Runtime environment kind. Omit or send an empty value for automatic selection.
, cloud, byoc BYOC Runner ID. Used only when environment_kind=byoc.
Whether to create and enable an HTTP POST trigger. When enabled, the response includes a one-time token.
Whether the On-call incident trigger is enabled.
On-call integration IDs to watch. Creating or enabling this trigger requires at least one valid ID.
x >= 1Incident severities to watch. Supported values are Critical, Warning, and Info; creating or enabling this trigger requires at least one value.
Critical, Warning, Info 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.