Actions34
- Cliente Actions
- Catálogo Actions
- Pedido Actions
- Conversa Actions
- Contexto Actions
- Telemetria Actions
- Canal WhatsApp Actions
- Paciente Actions
- Procedimento Actions
- Agenda Actions
- Agendamento Actions
- Lembrete Odonto Actions
Conversa → Anexar ao Handoff
AI-generatedSummary
Attach a literal file (image or PDF) to an existing conversation handoff that was previously closed with a 'needs human' status.
Inputs
- Token ID Dinamico — Optional dynamic token for multi-tenant bootstrap, must be used with the dynamic Signing Secret.
- Signing Secret Dinamico — Optional ephemeral signing secret returned by bootstrap; do not log or expose this value.
- Conversa ID (required) — UUID of the conversation returned when closing the conversation with 'precisa_humano' (needs human) status.
- Conteúdo Base64 Literal (required) — Literal file content as a base64 string or data URL from media relay; should never be sent to LLM or OCR.
- MIME — MIME type of the file; required if the content is base64 without a data URL prefix.
- Nome do Arquivo — Optional original filename of the attachment.
- Legenda Administrativa — Short literal text for reception purposes; do not describe or interpret the file content.
- Idempotency Key (required) — The real WhatsApp message ID to prevent duplicate file attachments.
Output shape
a JSON object representing the result of the attachment operation returned by the Núcleo API.
The operation is idempotent by the provided Idempotency Key to ensure no duplicate attachments occur. It requires a valid 'Conversa ID' corresponding to a conversation closed with human handoff. The file content must be base64-encoded or a data URL, and if using pure base64, the MIME type must be specified. No actual file parsing or interpretation is done by the node; the raw content is forwarded to the API.