Act on messages and bookings
update_plugin_dataDestructive
Act on plugin items (editor): mark messages (read, new, spam, not_spam, archive, bin, restore; read also takes get_account notice ids nt_… or all, only when the user asks) or a booking (add, edit details, approve, decline, cancel, reschedule, no_show, complete); decline, cancel, reschedule and an add or edit that emails the customer are two-step (confirm_token, then repeat).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| all | No | With action read: every notice (yours) or every new item of that kind, optionally on one site | |
| name | No | ||
| site | No | Not needed for notice ids or all | |
| No | |||
| force | No | Booking add, edit (party), reschedule: book even if it clashes | |
| notes | No | ||
| party | No | ||
| phone | No | ||
| start | No | Booking add, reschedule: local "2026-10-15T14:00" (booking time zone) or "now" | |
| action | Yes | ||
| series | No | Booking add: weekly repeat, count or until (YYYY-MM-DD); a 409 lists clashes (on_clash "skip", or force). Cancel: "rest" = this and later | |
| source | No | Booking add (default phone) | |
| answers | No | Booking add, edit: {question id: answer} for the settings' questions ("" removes one) | |
| message | No | Bookings: a note for the customer (reason) | |
| service | No | Booking add: service id or name | |
| item_ids | No | From list_plugin_data, or notice ids (nt_…) from get_account; one id for bookings; none for booking add | |
| resource | No | Booking add, reschedule: staff or room id or name (default any free) | |
| plugin_id | No | Not needed for notice ids or all | |
| confirm_token | No | From the first call, once the user said yes | |
| notify_customer | No | Booking: email the customer (default true when there is an email) |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | On failure (isError): {code, message} | |
| agent_message | No | ||
| confirm_token | No |