download_inbox_attachment
Behavior, inputs, outputs and permissions for download_inbox_attachment.
Reviewed · 2026-10-06 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “Behavior and boundaries”Creates and stores a one-use download ticket; requires inbox:read and inbox:write. Returns the ticket for a ready attachment ID. Request url with HTTP GET and Authorization: Bearer
Permissions
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
inbox:read, inbox:write
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "minLength": 1, "maxLength": 200 } }, "required": [ "id" ], "additionalProperties": false}Output
Section titled “Output”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "attachmentId": { "type": "string", "minLength": 1, "maxLength": 200 }, "url": { "type": "string", "format": "uri" }, "token": { "type": "string" }, "expiresAt": { "type": "number" }, "method": { "type": "string", "enum": [ "POST", "GET" ] } }, "required": [ "attachmentId", "url", "token", "expiresAt", "method" ], "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.