send_feedback
Behavior, inputs, outputs and permissions for send_feedback.
Reviewed · 2026-10-06 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “Behavior and boundaries”Requires feedback:write. Records and queues feedback the user explicitly asked to send: their own message, a category and whether they want a reply. It does not include chat history or calendar/contact content; the support delivery includes internal user and workspace references for support routing, and it never sends from the user’s own mailbox; it reaches Ridian’s existing support inbox. Only call it when the user asked for it in this request, never on your own initiative and never to report your own difficulty with a tool. Pass a stable requestId so a retry does not file the same feedback twice. The reply is a reference and received: the message is recorded, not yet confirmed delivered.
Permissions
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
feedback:write
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "message": { "type": "string", "minLength": 1, "maxLength": 4000 }, "category": { "type": "string", "enum": [ "bug", "idea", "question", "other" ] }, "wantsReply": { "type": "boolean" }, "locale": { "type": "string", "enum": [ "de", "en" ] }, "requestId": { "type": "string", "minLength": 8, "maxLength": 100 } }, "required": [ "message", "category", "wantsReply", "locale", "requestId" ], "additionalProperties": false}Output
Section titled “Output”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "ok": { "type": "boolean", "const": true }, "reference": { "type": "string" }, "status": { "type": "string", "enum": [ "received", "delivered" ] } }, "required": [ "ok", "reference", "status" ], "additionalProperties": false}Errors and retries
Section titled “Errors and retries”Check the tool result for errors. Do not blindly retry writes after a timeout. Check the current resource or send status first.