TOTVS REST API
The standard path in up-to-date environments. brisk4 consumes the REST endpoints exposed by Protheus, RM or Datasul, authenticated by token.
Integration · ERP
Official WhatsApp + TOTVS.
The brisk4 and TOTVS integration brings data that already lives in the ERP into the customer conversation. It covers Protheus, RM and Datasul, through the TOTVS REST API, webhooks or an intermediate layer when the environment is heavily customised.
What syncs
TOTVS objects inside the conversation.
| TOTVS object | Direction | Trigger |
|---|---|---|
| Sales order | TOTVS → brisk4 | Customer asks for status; brisk4 queries by order number or tax ID and answers with stage, ETA and carrier. |
| Receivable and invoice slip | TOTVS → brisk4 | Duplicate slip requested in chat, or an automatic reminder when the receivable approaches its due date. |
| Tax document | TOTVS → brisk4 | Invoicing the order triggers delivery of the tax document and its access key over WhatsApp. |
| Customer record | brisk4 ↔ TOTVS | Service identifies the customer by tax ID and writes contact and address changes back into the ERP. |
| Service order | brisk4 → TOTVS | A support request opened in the conversation becomes a service order in the ERP, with history and attachments included. |
Ready-made flows
What goes live first.
- Duplicate invoice slip with no queueThe customer requests a duplicate on WhatsApp, brisk4 validates the tax ID, queries the open receivable in TOTVS and returns the slip with barcode and digitable line. No finance team involved.
- Self-service order statusA query by order number or tax ID returns production stage, invoicing, carrier and tracking code, read straight from Protheus.
- Service order opened from chatAI runs the triage, identifies the equipment and the contract, opens the service order in the ERP and returns the ticket number in the same conversation.
How we connect
Method and prerequisites.
Event webhook
Invoicing, settlement and status changes fire the notification. Avoids polling and keeps messages timely.
Intermediate layer
For heavily customised environments or older versions, we design middleware or direct database reads during rollout.
- Covered products
- TOTVS Protheus, TOTVS RM and TOTVS Datasul
- Required access
- Integration user with read permission on the modules involved
- Environment
- TOTVS in the cloud or on-premise with the server reachable over the network
- Licensing
- API module or user, according to your TOTVS contract
- Write scope
- Defined during rollout, approved by your IT team
- Staging
- ERP test environment before any production call
Frequently asked questions
TOTVS and brisk4: questions.
Does brisk4 integrate with TOTVS Protheus?
Yes. Integration with TOTVS Protheus runs through the ERP REST API, through event webhooks or through an intermediate layer when the environment carries heavy customisation. The most common objects are sales order, receivable, tax document, customer record and service order.
Does it also cover RM and Datasul?
Yes. The same method applies to TOTVS RM and TOTVS Datasul. What differs between product lines are the endpoints and object names, mapped during rollout with your team.
Do I need to install anything on my TOTVS server?
In most cases, no. An integration user with read permission and a network-reachable server are enough. Environments with no available API may require an intermediate component, defined during the assessment.
Can customers pull a duplicate invoice slip themselves?
Yes, and it is one of the most requested flows. The customer asks on WhatsApp, brisk4 validates their identity, queries the open receivable in TOTVS and returns the slip with a digitable line, with no finance team in the loop.
See it running on your TOTVS.
In the free assessment a specialist maps your TOTVS product line, what it exposes and which flow pays off fastest.