entities and notifications lists, when provided, replace the whole set — pass the complete new list, not a delta. Entities are passed as slugs from the resolve tools, exactly as in particle_alert_create; each is re-resolved to its (entity_type, entity_id) internally. Use is_active to pause or resume an alert without deleting it.
An alert’s kind is fixed at creation — to watch for a different signal (mention vs. speaker appearance), create a new alert.
Inputs
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
alert_id | string | yes | — | Alert id to update. |
title | string | no | unchanged | New title. |
description | string | no | unchanged | New description. |
delivery_cadence | enum | no | unchanged | New delivery cadence: REALTIME, DAILY, or WEEKLY. |
is_active | boolean | no | unchanged | Pause (false) or resume (true) the alert. |
entities | array of strings | no | unchanged | Replacement watch list as entity slugs (from the resolve tools). When provided, replaces the entire existing set; omit to leave entities unchanged. |
notifications | array of strings | no | unchanged | Replacement notification emails. When provided, replaces the entire existing set; omit to leave them unchanged. |
Output
A markdown document rendering the updated alert’s full configuration — the same shape returned byparticle_alert_create and particle_alert_get: title H2, **ID:**, **Kind:**, **Delivery:**, **Status:**, optional **Description:**, a ### Watching (N) entity list, and a **Notify:** row.
Passing output_format: "json" returns the same fields as compact JSON.
Example
Related
- REST equivalent:
PATCH /v1/alerts/{id}. - Resolve replacement watch targets with
particle_entity_resolve,particle_person_resolve, orparticle_company_resolve. - To change an alert’s
kind, create a new one withparticle_alert_create. - To remove an alert entirely, use
particle_alert_delete.