Connector overview
The 14 source types and 13 destination types in the engine, and which of them are exposed in the IntuCloud beta today.
Last updated August 12, 2026
On this page
The intu-dev engine ships 27 connector types: 14 sources and listeners, and 13 destinations. Self-hosted deployments can use all of them. The IntuCloud beta exposes a subset, and this page is explicit about which.
Sources and listeners (14)
| Connector | Cloud beta |
|---|---|
| HTTP | Available |
| TCP (raw / MLLP) | Available — MLLP over TLS |
| FHIR (R4 / STU3 server) | Available |
| SOAP | Available |
| IHE (XDS.b, PIX, PDQ over HTTP) | Available |
| File (local / FTP / S3 / SMB) | Coming soon — engine-supported |
| SFTP | Coming soon — engine-supported |
| Kafka | Coming soon — engine-supported |
| Database (Postgres / MySQL / MSSQL / SQLite) | Coming soon — engine-supported |
| Email (IMAP / POP3) | Coming soon — engine-supported |
| DICOM (C-STORE SCP) | Coming soon — engine-supported |
| FHIR Poll | Coming soon — engine-supported |
| FHIR Subscription (R4B) | Coming soon — engine-supported |
| Channel | Coming soon — engine-supported |
The pattern is worth naming: the connectors available in the cloud beta are the ones where IntuCloud receives an inbound connection at a gateway. Poller and consumer types — the ones that reach out to a database, a mailbox, a bucket or a broker — and DICOM listeners are implemented in the engine but not yet exposed in the cloud.
Destinations (13)
| Connector | Cloud beta |
|---|---|
| HTTP | Available |
| FHIR | Available |
| TCP (raw / MLLP) | Available |
| Kafka | Available |
| Database | Available |
| File | Available |
| SFTP | Available |
| SMTP | Available |
| Direct | Available |
| Log | Available |
| DICOM (C-STORE SCU) | Coming soon — engine-supported |
| JMS (ActiveMQ) | Coming soon — engine-supported |
| Channel | Coming soon — engine-supported |
What “engine-supported” means
It means the connector is implemented, tested and usable today — on the open-source engine, on your own infrastructure. It is not a roadmap aspiration. What is pending is cloud exposure: the gateway, networking and operational work needed to run that connector type as a managed service.
If you need one of these now, self-hosting intu-dev is a supported path, and the project you build in IntuCloud exports directly.
Each destination has its own hooks
Regardless of type, every destination carries a filter, a transformer and a response transformer. A channel fanning out to three systems shapes three different payloads without forking the source logic. See The pipeline model.
The full catalog with protocol notes is on the connectors page.