Núcleo Wondai icon

Núcleo Wondai

Atendimento de IA no Núcleo Wondai: preparar conversa (GATE liga/desliga + contexto operacional ANTES da LLM), buscar cliente, resolver catálogo (fuzzy), criar/alterar/cancelar pedido, consultar contexto e registrar conversa. Assinatura HMAC; o tenant vem do token.

Actions34

Pedido → Anexar Comprovante

AI-generated

Summary

Attach a payment proof document (image or PDF) to an existing order in the tenant's system to notify the team for verification without processing the payment automatically.

Inputs

  • Pedido ID (required) — The identifier of the order within the tenant; orders from other bakeries return 404.
  • Comprovante (Base64 ou pending:<uuid>) (required) — The payment proof sent by the customer, preferably as an opaque handle 'pending:' from the Evolution relay. Also accepts data-URL or raw base64 (if base64, the MIME type must be provided). Limits are 5 MB; supported formats are PNG, JPG, WEBP, and PDF.
  • MIME (se base64 puro) — Required only if the proof content is raw base64; leave empty if data-URL or 'pending:' handle is used. Specifies the MIME type of the file.
  • Nome do arquivo — Optional original file name (e.g., 'comprovante-pix.pdf') to help the team recognize the attachment.
  • Legenda — Optional short caption or comment accompanying the proof (e.g., 'Pago às 19:46').
  • Token ID Dinamico — Optional dynamic token returned by multi-tenant bootstrap; must be used together with the dynamic Signing Secret.
  • Signing Secret Dinamico — Optional ephemeral secret returned by bootstrap; must not be logged or output.
  • Idempotency Key — Optional key to prevent duplicate attachments on retries; use the same key (e.g., a WhatsApp messageID) for repeated attempts.

Output shape

a single JSON response object from the API indicating success or failure of the attachment request

The operation is idempotent using the Idempotency Key if provided, preventing duplicate attachments on retries. The actual payment verification and processing are done manually by the team; the system only stores the literal file securely in a private bucket.

Examples

Example 1: Attach a payment proof PDF received from a customer after order confirmation to the order for manual verification.

Set 'Pedido ID' to the existing order UUID, provide the 'Comprovante' as a 'pending:' handle from the Evolution relay or base64-encoded PDF data, optionally supply the MIME type 'application/pdf', add an optional file name and caption, and use the same Idempotency Key if retrying.

Links

Discussion