You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(incidentio): align declared outputs and enum hints with the v2 API (#7306)
* fix(incidentio): align declared tool outputs and enum hints with the v2 API
Four declared outputs could never be populated because the v2 API names the
field differently, and three param descriptions advertised enum values the
API rejects. Verified against https://api.incident.io/v1/openapiV3.json,
which serves the v1/v2/v3 schemas in one document.
- IncidentV2 has `permalink`, not `incident_url`, and no `description` at
all: incidents list/create/update/show now declare and map `permalink`
and drop `description`.
- IncidentUpdateV2 has `new_incident_status` (required), not an optional
`new_status`; `message` is optional, `updated_at` is not returned, and
`updater` is an actor wrapper whose user lives under `updater.user`.
- EscalationV2 has `title` and `status`, not `name`.
- WorkflowsCreate/UpdateWorkflowPayloadV2 accept only `newly_created` and
`newly_created_and_active` for `runs_on_incidents`, and
CustomFieldsCreatePayloadV2 accepts only text, link, numeric,
single_select and multi_select for `field_type`.
Renaming a declared output changes the reference-picker surface for these
tools; nothing in the repo read the old names.
* fix(incidentio): stop the block offering rejected enum values and declare every actor branch
| ↳ `call_url`| string | URL for the incident call/bridge |
211
206
| ↳ `severity`| object | Severity of the incident |
@@ -221,7 +216,7 @@ Update an existing incident in incident.io. Can update name, summary, severity,
221
216
| ↳ `name`| string | Type name |
222
217
| ↳ `created_at`| string | Creation timestamp |
223
218
| ↳ `updated_at`| string | Last update timestamp |
224
-
| ↳ `incident_url`| string |URL to the incident |
219
+
| ↳ `permalink`| string |Permalink to the incident in incident.io|
225
220
| ↳ `slack_channel_id`| string | Associated Slack channel ID |
226
221
| ↳ `slack_channel_name`| string | Associated Slack channel name |
227
222
| ↳ `visibility`| string | Incident visibility |
@@ -486,7 +481,7 @@ Create a new workflow in incident.io.
486
481
|`trigger`| string | No | Trigger type for the workflow \(e.g., "incident.updated", "incident.created"\)|
487
482
|`steps`| string | No | Array of workflow steps as JSON string. Example: \[\{"label": "Notify team", "name": "slack.post_message"\}\]|
488
483
|`condition_groups`| string | No | Array of condition groups as JSON string to control when the workflow runs. Example: \[\{"conditions": \[\{"operation": "one_of", "param_bindings": \[\], "subject": "incident.severity"\}\]\}\]|
489
-
|`runs_on_incidents`| string | No | When to run the workflow: "newly_created" \(only new incidents\), "newly_created_and_active" \(new and active incidents\), "active" \(only active incidents\), or "all" \(all incidents\)|
484
+
|`runs_on_incidents`| string | No | When to run the workflow: "newly_created" \(only newly created incidents\) or "newly_created_and_active" \(newly created and already active incidents\)|
490
485
|`runs_on_incident_modes`| string | No | Array of incident modes to run on as JSON string. Example: \["standard", "retrospective"\]|
491
486
|`include_private_incidents`| boolean | No | Whether to include private incidents |
492
487
|`continue_on_step_error`| boolean | No | Whether to continue executing subsequent steps if a step fails |
@@ -569,7 +564,7 @@ Update an existing workflow in incident.io.
569
564
|`name`| string | Yes | New name for the workflow \(e.g., "Notify on Critical Incidents"\)|
570
565
|`steps`| string | Yes | Complete array of workflow steps as a JSON string |
571
566
|`condition_groups`| string | Yes | Complete array of workflow condition groups as a JSON string |
572
-
|`runs_on_incidents`| string | Yes | When to run the workflow: newly_created, newly_created_and_active, active, or all|
567
+
|`runs_on_incidents`| string | Yes | When to run the workflow: newly_createdor newly_created_and_active|
573
568
|`runs_on_incident_modes`| string | Yes | Complete array of incident modes to run on as a JSON string |
574
569
|`include_private_incidents`| boolean | Yes | Whether to include private incidents |
575
570
|`continue_on_step_error`| boolean | Yes | Whether to continue executing subsequent steps if a step fails |
@@ -783,11 +778,15 @@ List all escalation policies in incident.io
783
778
784
779
| Parameter | Type | Description |
785
780
| --------- | ---- | ----------- |
786
-
|`escalations`| array | List of escalation policies |
787
-
| ↳ `id`| string | The escalation policy ID |
788
-
| ↳ `name`| string | The escalation policy name |
789
-
| ↳ `created_at`| string | When the escalation policy was created |
790
-
| ↳ `updated_at`| string | When the escalation policy was last updated |
781
+
|`escalations`| array | List of escalations |
782
+
| ↳ `id`| string | The escalation ID |
783
+
| ↳ `title`| string | The escalation title |
784
+
| ↳ `status`| string | The current escalation status |
785
+
| ↳ `description`| string | Additional detail provided with this escalation |
786
+
| ↳ `priority`| object | The escalation priority |
787
+
| ↳ `name`| string | Priority name |
788
+
| ↳ `created_at`| string | When the escalation was created |
789
+
| ↳ `updated_at`| string | When the escalation was last updated |
0 commit comments