feat: send order situações to Tiny for the client's WhatsApp notices
All checks were successful
Build and deploy / Validate source (push) Successful in 5s
Build and deploy / Integration suite on a real stack (push) Successful in 2m5s
Build and deploy / Secret scan and release gate (push) Successful in 5s
Build and deploy / Publish images (push) Successful in 1m45s
All checks were successful
Build and deploy / Validate source (push) Successful in 5s
Build and deploy / Integration suite on a real stack (push) Successful in 2m5s
Build and deploy / Secret scan and release gate (push) Successful in 5s
Build and deploy / Publish images (push) Successful in 1m45s
The client already sends WhatsApp notices from Tiny's order situação (Tiny webhook -> middleware -> n8n). With TINY_STATUS_UPDATES on, a paid order is set to "Aprovada" once and a finished pickup order to "Pronto para envio"; pickup orders carry the client's pickup forma de envio (TINY_FORMA_ENVIO_RETIRADA). The ready event now carries the order and the Tiny id from the sale's receipt. Off by default until go-live, when n8n stops sending the DTFIMP designer message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -308,6 +308,30 @@ From the report already sent. These are dated promises, not backlog.
|
||||
the two Têxtil modes; UV needs a product either way. The item note already
|
||||
carries the Site mode and grade. No product ids are set in production yet;
|
||||
both questions go to the client with the Mercado Pago credentials request.
|
||||
**Customer notices through Tiny (2026-09-25, Week 3 head start):** the client
|
||||
already sends WhatsApp notices from Tiny's order situação (Tiny webhook ->
|
||||
the `api-tiny-n8n` middleware, which reads the order through API v2 -> n8n
|
||||
-> WhatsApp templates): Aprovado, Pronto para envio with forma de envio `X`
|
||||
(v2 "Customizada", their pickup), Enviado, Entregue. So the system's own
|
||||
WhatsApp sender stays off and Tiny drives the notices. With
|
||||
`TINY_STATUS_UPDATES=true` a paid order is created "Aberta" and set to
|
||||
"Aprovada" (a retry finishes a half-done approval; an order already moved on
|
||||
is left alone), and moving a pickup order to Finalizado sets "Pronto para
|
||||
envio" by the Tiny id from the sale's receipt, searching only when it is
|
||||
missing and retrying while the sale has not reached Tiny. Pickup orders
|
||||
carry `TINY_FORMA_ENVIO_RETIRADA` (`tiny_probe formas-envio` lists the ids;
|
||||
"Testar conexão" now checks it). Delivery orders get "Enviada" with 1.2.
|
||||
Off by default: while n8n's `isDTFIMP` branch exists, "Aprovado" on a
|
||||
`DTFIMP` product sends the designer message, and the Site's Têxtil product
|
||||
code starts with `DTFIMP`. **Go-live together:** `TINY_ADAPTER=tiny`,
|
||||
`TINY_STATUS_UPDATES=true`, n8n's `isDTFIMP`/"DTF Aprovado - Designer"
|
||||
removed with "Mapear Whatsapp do Vendedor" connected to `If6`, and the
|
||||
middleware's `numero_ecommerce` falling back to the purchase order so the
|
||||
message shows `DTF-<n>`. **Unverified on the account:** that an API status
|
||||
change fires Tiny's webhook, that Tiny accepts Aprovada -> Pronto para envio
|
||||
without Faturada, and the v2 field name for the purchase order. Correção
|
||||
necessária and Produção iniciada have no Tiny situação; client to decide
|
||||
whether they need messages.
|
||||
- `[~]` 1.4 — Final print-file generation (see 3.2 and 3.6: production instructions
|
||||
must survive checkout before an output engine can reproduce the approved job).
|
||||
**Built (2026-09-24):** each paid item gets a PDF the width of the film and
|
||||
|
||||
Reference in New Issue
Block a user