One platform, one console.

Low-code builder, connectors, runs and logs, and Floui Database in one place. No modules sold separately.

Builder, connectors, runs, and Floui Database in one place.

Contact

We only use your data to reply.

Contact

0 / 180

We only use your data to reply.

Workflows

Connectors

Runs

Database

Governance

Workspace / OperationsExample
WorkflowLast runStatus
Order → ERPShopify · Linx Microvix2 min agoActive
Inventory → e-commerceLinx Microvix · Shopify5 min agoActive
Customers → CRMShopify · HubSpot1 h agoActive
Product loadSFTP · Floui DatabaseyesterdayPaused

Illustrative example.

Fully managed or self-serveFully managed or self-serve
Specialist team, depending on the plan
400+ connectors; others on demand, after an API and connectivity check

All in one product, ready for the enterprise.

All in one

  • Data and integration orchestration
  • Microservices and APIs
  • Events and messaging
  • Data processing

Easy to use

  • Low-code builder
  • Serverless code in JavaScript and Python
  • Internal or external database and storage
  • Template gallery

Ready for the enterprise

  • Monitoring
  • Audit logs
  • Resource isolation
  • Scale with volume

Low-code builder.

Design, test, and publish workflows in the visual editor, without complex deploys. When a rule needs it, write code.

  • Visual editor with ready-made components
  • JavaScript and Python functions
  • Reusable sub-workflows and templates
  • Custom connectors for legacy systems

Runs and logs.

Follow each workflow run: what executed, what is active, and the log of each integration.

  • Execution history
  • Log of each workflow step
  • Filter by workflow and status
14:32Order #10482Completed
14:31Order #10481Error
Runs / Order → ERPExample
TimeRecordStatusDuration
14:32:08Order #10482Completed1,2 s
14:31:55Order #10481Error · view log0,4 s
14:29:40Order #10480Completed0,9 s
14:25:12Order #10479Completed1,1 s
14:31:55  Send order · Linx Microvix
          response 422 · field "cliente.cep" empty

Illustrative example.

Connectors.

ERPs, e-commerce, marketplaces, CRMs, and logistics, ready to use in workflows. For the rest, universal connectors.

View the catalog
Universal:
HTTPS / RESTSFTP and filesCSV and XMLJSON to XML/XLSXEmailQueuesSchedulers+ custom connectors

Build your own connector

A system outside the catalog. HTTP, file, database, or queue, in the workspace library.

Connectors / New connectorExample
NameInternal system
Base URLhttps://api.example.com
AuthenticationToken · workspace variable

operations

When an order changes triggerscheduled query
List orders actionGET /orders
Create order actionPOST /orders

Illustrative example.

Build your own connector.

A system outside the catalog? Your team builds the connector in the builder and uses it in any workflow.

  • Set the URL, the authentication, and the endpoints
  • Define the operations: triggers and actions
  • Reuse the connector in the workspace workflows
  • Prefer not to build it? The Floui team builds it, depending on the plan

Simple management, everything in view.

Runs, logs, alerts, and permissions in the same console.

Runs

What ran and what is active, by workflow.

Order #1048214:32
Order #1048114:31
Logs

The detail of each step, to find the cause quickly.

422 · field "cep" empty
Send order · step 3
Alerts

A notice to the team when a workflow fails.

Error in Order → ERP
email
Permissions

Who can view, edit, and publish, by workspace.

Anaadmin
IT teameditor

Floui Database.

Tables in the console, for use in workflows, instead of external data sources.

  • Create the structure and edit the data in the console
  • Field mapping, auxiliary records, and control
  • Used by integrations, automations, and APIs
Database / status_mapExample
status_ecommercestatus_erpactive
paidRELEASEDyes
shippedINVOICEDyes
canceledCANCELEDyes
returnedRETURNyes

Sample data.

You choose who runs it.

Operating models

Fully managed

Our team implements, runs, and maintains the integrations, depending on the plan.

  • Field mapping and implementation by the specialist team, depending on the plan
  • Adjustments when the systems change
  • Your team stays on the business

Self-serve

Your team uses the platform; specialists support you when you need them, depending on the plan.

  • Training to use the platform
  • Low-code builder and code when you need it
  • More control over the solution

Security and governance.

Information security

  • Resource isolation
  • Credentials in variables, outside the workflows

Infrastructure

  • Managed platform, no server to run
  • Serverless code execution

Governance

  • Workspaces by team or project
  • Users, groups, and service accounts
  • Audit logs

Security and governance

FAQ

What does the Floui platform offer?
A low-code builder to create and maintain integrations (workflows, triggers, and code when you need it), with workspaces, audit logs, alerts, and versioning. Depending on the plan, the specialist team can run this fully managed.
Do I need to know how to code to use Floui?
No. Most of the work is in the low-code builder. When a workflow needs custom logic, you can use JavaScript or Python, or the specialist team can handle it, depending on the plan.
How do I follow what the integrations are doing?
With audit logs, email or webhook alerts, and workflow history. IT and e-commerce teams see what ran, what failed, and what needs attention.
Can I have separate environments by team or project?
Yes. Workspaces organize workflows and access by context, so each area works in its own space without mixing operations.

See the platform with a specialist.

A conversation about your systems and processes.

We only use your data to reply.

Contact

0 / 180

We only use your data to reply.

Talk to a specialist