statements opens attached to the
request, exactly as from the statement page in the web app, and a record narrows
it to one deal of that statement. One request can cover several statements —
open one per question, not one per statement. A statement is linked once, about
one of its records at most. The caller is the request’s author, and message is
posted in their name.
Only a request’s members are notified of its messages, and most users see only
the requests they belong to — so list in member_ids everyone who should follow
it: the user whose statement it is about, anyone message @-mentions. A mention
alone neither adds nor notifies them. Close, reassign or re-file the request
later with update_request.
Attachments are not supported here.
Available only where the Qobra write tools beta is enabled. Every write is
recorded in the audit trail as the Qobra MCP agent.
Parameters
Body
Body
string
required
Title of the request, as it reads on the requests board — ‘January
commission looks low’. Keep it short; the detail goes in
message.string
First message to post in the thread, written as the caller. Plain text, as
in the web app: anything between
< and > is removed, so write no HTML
and spell comparisons out in words. Omit to open the request with an empty
thread.object[]
The statements the request is about — one user in one month each, optionally
narrowed to one of its records. Omit for a request about no statement in
particular.
string
Id of the topic to file the request under — one of
requests.topics from
get_company_settings. Omit to file it under no topic. The call is refused
when the company defines no topics, or when the id names none of them; the
refusal lists the available topics and their ids.string[]
Ids or emails of the people to add to the request as participants, beside
its author — as list_users returns them. Emails match case-insensitively.
Each one can read and answer the thread, is
notified they were added, and appears in the request’s
members. Omit to
open the request with its author as the only member.string
Id or email of the person to assign the request to — the one expected to
handle it, as list_users returns it. They become a member and are notified it is
theirs. Omit to leave it unassigned, as the web app opens a request.