MCP: push

Queue a transactional push notification (text + optional url buttons) to a user's private chat on their messenger, with a copy in the user's Open Lines topic. To get a decision from the user, ask in the text and read the reply with get_conversation, which needs the dialogs:read scope; a confirmation is then carried out with the matching tool. Callback buttons are not available here: they are a REST integration mechanism of an ExternalApp key subscribed to the button.clicked webhook. For promotional messages use broadcasts. Media is not delivered and is refused; a push is dropped if not handed over for delivery within 24 hours; while push notifications are switched off the call is refused.

Scopes (ALL): ["push"]. Risk: "write".

Вход, результат и права

Set the status of ONE submission, by its own `seq_num` (returned by `pull_form_submissions` — not the form's number or the public code): `handled: true` marks it dealt with (🟢), `handled: false` returns it to new (🔵). This is what the owner's operators see: the card in their Telegram topic switches and records that YOUR integration changed it, by name. Answers `outcome`: `changed` — you changed it; `unchanged` — it was already in that state (an operator, or an earlier call of yours, set it) and nothing changed; `not_found` — no such submission in this account. 🔴 Report `unchanged` as no work done by you. Safe to retry: a repeat call changes nothing.

Scopes (ALL): ["push:form_submissions"]. Risk: "write".

Вход, результат и права

Submit answers to one of this business's forms by `form_seq_num`. The caller tenant is always taken from the API key; do not provide a client id. The form's declared submission schema is enforced before the lead is stored. Returns the new submission own `seq_num` and its separate public `submission_code`. This call creates a new submission every time and is not idempotent.

Scopes (ALL): ["push:form_submissions"]. Risk: "write".

Вход, результат и права