Out-of-the-box Camel connectors

What it is

Flowable now ships a set of ready-to-use integration connectors built on Apache Camel, so a process or case can send and receive data over common transports without custom integration code or a separate integration layer. This release delivers connectors for files, FTP/SFTP, SQL databases and Azure Service Bus.

Each connector is configured as an inbound or outbound channel in Flowable Design and runs on the platform, so integrations are modeled and governed in the same place as the rest of your work.

What’s included:

• File connector: read and write files from a local or mounted directory.
• FTP / SFTP connector: exchange files with remote servers over FTP and SFTP.
• SQL connector: Poll from and write to relational databases.¹
• Azure Service Bus connector: send and receive messages on Azure Service Bus.
• All built on Apache Camel and wired in as inbound and outbound channels through the event registry.

Why it matters

Real business processes rarely live in isolation. They pick up files from a drop folder, poll an SFTP server, read a database, or exchange messages on a bus. Shipping these as out-of-the-box connectors means a team integrates with the systems it already runs without writing integration code or standing up a separate integration layer, which shortens time to value and keeps the integration inside the governed platform.

How it works

Each connector is configured as an inbound or outbound channel in Flowable Design, backed by an Apache Camel endpoint. Inbound channels turn an incoming file, message or row into an event that starts or correlates to a process or case; outbound channels send data out over the same transports.

Example

A process needs to pick up invoices dropped on an SFTP server. You configure an inbound SFTP channel that polls the directory, and each new file starts a case with the file captured as content. When the case is decided, an outbound Azure Service Bus channel publishes the outcome to a downstream system. There is no custom integration code, it is all configured in Design and runs on the platform.