Rastro for Bling

Rastro for Bling puts your customer's Bling ERP orders next to the conversation, so agents stop switching tabs to answer "where is my order?".

What agents see in the ticket sidebar

• The Bling customer matched to the ticket requester (by e-mail, CPF or CNPJ), or a search box to look up another one

• The customer's latest orders with their Bling status

• NF-e details with a link to the DANFE

• Tracking codes (one tap to copy)

• Pending boleto and Pix charges, with links to pay

The app is read-only: it never creates or changes anything in Bling or in Zendesk.

About us

1808 Devs builds support tooling for Brazilian e-commerce teams.

Data disclosure

• Zendesk data accessed: the ticket requester's name, e-mail address and, optionally, one custom user field you choose (for CPF/CNPJ). Read only, in the agent's browser, to find the customer in Bling.
• Data sent to our service: the e-mail/CPF/CNPJ being searched, your Bling Client ID, and a signed request token. Bling order data is fetched live from Bling and returned to the agent's browser; we do not store customer or order data.
• Data we store: only the credentials needed to talk to your Bling account: your Bling Client ID and Client Secret and the OAuth access/refresh tokens, encrypted at rest (AES-256-GCM). They are deleted when an admin clicks "Disconnect Bling" in the app, or automatically after 60 days without use (for example, after uninstalling).
• Logs: we keep no request logs; error events record only a code and status (no customer data, e-mail addresses, documents or tokens).
• Full policy: https://1808devs.vercel.app/privacy