REST API
The preferred path. brisk4 consumes and exposes REST endpoints authenticated by token or OAuth 2.0, with JSON payloads. On-demand queries, inside the conversation.
Integrations
Official WhatsApp talking to your ERP.
brisk4 connects omnichannel customer service to the systems already running in your company: ERP, CRM, marketing platforms and databases. Integration happens through REST APIs, webhooks, dedicated connectors or direct database access, depending on what your system exposes.
Methods
Three ways to connect.
There is no impossible integration, only systems that expose no interface. If yours exposes any of these three, brisk4 can talk to it.
Webhooks
For events born in your system: order invoiced, invoice settled, ticket closed. The ERP notifies brisk4 and the message goes out immediately, with no polling.
Database and middleware
For legacy systems with no API. Direct reads on SQL Server, PostgreSQL, MySQL or Oracle, or an intermediate layer designed during rollout.
Integration pages
Detail by system.
WhatsApp + TOTVS
Protheus, RM and Datasul connected to customer service.
WhatsApp + SAP
S/4HANA, Business One and ECC in customer service.
WhatsApp + Salesforce
Leads, opportunities and cases in sync.
WhatsApp + RD Station
RD Marketing and CRM wired to WhatsApp.
WhatsApp + Bling
E-commerce orders, stock and invoices in chat.
WhatsApp + HubSpot
Contacts, deals and tickets in one flow.
Legacy and proprietary ERP
Old system with no API? It still connects.
REST API and webhooks
The technical base of every brisk4 integration.
Frequently asked questions
Questions about integration.
Does brisk4 integrate with any ERP?
brisk4 integrates with any system that exposes an integration interface: REST API, SOAP, webhook, structured file or database access. That covers practically every ERP on the market and most proprietary systems. Fully closed systems with no interface at all require an intermediate layer, assessed case by case.
How long does an integration take?
It depends on the system and the scope. A simple query over a documented REST API usually goes live within days. Bidirectional integration with a legacy ERP, multiple objects and business rules is a multi-week project, designed alongside your IT team during rollout.
Is the integration bidirectional?
It can be. brisk4 reads data from your system to answer the customer and also writes back: it creates the service record, updates the customer file, opens the ticket or logs the opportunity. Write scope is defined with you, because it involves permissions and business rules.
Do I need an extra ERP licence?
Some vendors charge for the API module or for an integration user. That is a condition of your contract with the ERP vendor, not with brisk4. We check this during the assessment, before any proposal.
Is my ERP data stored inside brisk4?
Only what the service flow requires. Point queries such as order status run in real time and leave no copy behind. What is stored is the conversation history and contact data, under LGPD rules.
Let us look at your case.
In the free assessment a specialist maps which systems you run, what each one exposes and which integration pays off first.