Connect TOTVS Fluig to the systems that are part of your operation
We develop and adjust integrations between TOTVS Fluig and APIs, ERPs, internal systems, platforms, and external services to keep data and processes connected consistently.- Fluig
- APIs
- REST
- SOAP
Problems that indicate this need
Some common scenarios where this type of work can help.
The Fluig process depends on data from another system
Information needs to be queried during the workflow, but the integration does not exist or does not work correctly.
Data needs to leave Fluig for another application
An approval or activity performed in Fluig needs to create or update information in another system.
The integration works only in some scenarios
Communication failures, incomplete rules, or insufficient error handling leave processes inconsistent.
The team needs to check information between systems
The lack of proper integration forces users to compare or transfer information manually.
Capabilities applied to the scenario
The work is defined according to the problem, the existing environment, and the agreed scope.
- 01
API and WebServices consumption
Integration of Fluig with REST, SOAP, and other interfaces provided by the systems involved.
- 02
External data queries
Making external information available to forms, decisions, and processes inside Fluig.
- 03
Data submission
Creation or update of information in external systems from Fluig events and processes.
- 04
Integration datasets
Structuring datasets responsible for querying or mediating external information.
- 05
Rules and failure handling
Validations, messages, records, and behaviors for success and error scenarios.
What can come out of this work
Final deliverables depend on the scope, the systems involved, and the needs identified.
- Mapping of the data flow between Fluig and the systems involved
- Integrations planned in the scope
- Datasets or services required on the Fluig side
- Handling of the defined error scenarios
- Business rules associated with the integration
- Relevant technical documentation
Common questions
Can Fluig be integrated with any system?
It depends on the interfaces provided by the system involved. APIs, WebServices, files, and other mechanisms can be used according to the environment and available permissions.
Is it possible to fix an integration that already exists?
Yes. The work can start by analyzing the current integration to identify failures, dependencies, and points that need adjustment.
Do integrations need to use REST?
No. The approach depends on the available interfaces. Fluig can participate in integrations using REST, SOAP, WebServices, datasets, and other mechanisms appropriate to the scenario.
Does Fluig still depend on checking or rework between systems?
Let's map the data flow and understand where the integration needs to be created or fixed.