Skip to content
IntuCloud is built on the open-source intu-dev engine — star it on GitHub

Platform

27 connector types, and an honest list of what runs where.

14 sources and 13 destinations ship in the intu-dev engine. Some listener types are not exposed in the cloud beta yet — they are marked below rather than quietly omitted.

14

Source / listener types

13

Destination types

27

Total connector types

Reading the cloud column. “Available” means the connector is live in the IntuCloud beta today. “Coming soon (engine-supported)” means the open-source engine implements it and self-hosted deployments can use it now, but it is not yet exposed in the cloud — DICOM listeners and the polling and consumer connectors are in this group. Self-hosted intu-dev supports every entry on this page.

Catalog

Sources and listeners

14 ways a message can enter a channel.

  • Connector
    HTTP
    Protocols and notes
    HTTP/S listener — JSON, XML, form and raw bodies; basic, bearer, API key and OAuth2 auth.
    Cloud
    Available
  • Connector
    TCP (raw / MLLP)
    Protocols and notes
    HL7 v2 over MLLP or raw TCP framing, with ACK/NACK generation. MLLP over TLS in the cloud.
    Cloud
    Available
  • Connector
    FHIR
    Protocols and notes
    FHIR R4 / STU3 server endpoint accepting resources and bundles.
    Cloud
    Available
  • Connector
    SOAP
    Protocols and notes
    SOAP 1.1/1.2 web-service listener with WSDL-described operations.
    Cloud
    Available
  • Connector
    IHE
    Protocols and notes
    IHE ITI transactions over HTTP — XDS.b (ITI-41/42/43), PIX (ITI-8/9), PDQ (ITI-21/22).
    Cloud
    Available
  • Connector
    File (local / FTP / S3 / SMB)
    Protocols and notes
    Polls a directory or bucket and reads new files as messages.
    Cloud
    Coming soon (engine-supported)
  • Connector
    SFTP
    Protocols and notes
    Polls a remote SFTP path with key or password authentication.
    Cloud
    Coming soon (engine-supported)
  • Connector
    Kafka
    Protocols and notes
    Consumer group subscribing to one or more topics; SASL and TLS supported.
    Cloud
    Coming soon (engine-supported)
  • Connector
    Database
    Protocols and notes
    Polling reader for Postgres, MySQL, MSSQL and SQLite with a claim/mark-processed pattern.
    Cloud
    Coming soon (engine-supported)
  • Connector
    Email (IMAP / POP3)
    Protocols and notes
    Reads messages and attachments from a mailbox.
    Cloud
    Coming soon (engine-supported)
  • Connector
    DICOM
    Protocols and notes
    C-STORE SCP listener receiving DICOM instances on a configured AE title and port.
    Cloud
    Coming soon (engine-supported)
  • Connector
    FHIR Poll
    Protocols and notes
    Scheduled search against a FHIR server, paging results into the channel.
    Cloud
    Coming soon (engine-supported)
  • Connector
    FHIR Subscription
    Protocols and notes
    FHIR R4B subscription endpoint receiving notifications from a subscribing server.
    Cloud
    Coming soon (engine-supported)
  • Connector
    Channel
    Protocols and notes
    Receives messages handed off from another channel in the same project.
    Cloud
    Coming soon (engine-supported)

Catalog

Destinations

13 ways a message can leave a channel, each with its own filter, transformer and response transformer.

  • Connector
    HTTP
    Protocols and notes
    POST/PUT to any HTTP endpoint with configurable headers, auth and retry policy.
    Cloud
    Available
  • Connector
    FHIR
    Protocols and notes
    Create, update and conditional-upsert operations against a FHIR R4 server.
    Cloud
    Available
  • Connector
    TCP
    Protocols and notes
    HL7 v2 over MLLP or raw TCP to a downstream interface, with ACK handling.
    Cloud
    Available
  • Connector
    Kafka
    Protocols and notes
    Produces to a topic with configurable keys, partitioning and SASL/TLS.
    Cloud
    Available
  • Connector
    Database
    Protocols and notes
    Parameterised inserts and updates against Postgres, MySQL, MSSQL or SQLite.
    Cloud
    Available
  • Connector
    File
    Protocols and notes
    Writes messages to a local path, network share or S3 bucket.
    Cloud
    Available
  • Connector
    SFTP
    Protocols and notes
    Uploads to a remote SFTP path with key or password authentication.
    Cloud
    Available
  • Connector
    SMTP
    Protocols and notes
    Sends email with the message body or rendered content as an attachment.
    Cloud
    Available
  • Connector
    Direct
    Protocols and notes
    Direct secure messaging to a Direct address via a configured HISP.
    Cloud
    Available
  • Connector
    Log
    Protocols and notes
    Writes the message to the channel log — useful while building and debugging.
    Cloud
    Available
  • Connector
    DICOM
    Protocols and notes
    C-STORE SCU sending instances to a remote DICOM node.
    Cloud
    Coming soon (engine-supported)
  • Connector
    JMS (ActiveMQ)
    Protocols and notes
    Publishes to a JMS queue or topic on ActiveMQ.
    Cloud
    Coming soon (engine-supported)
  • Connector
    Channel
    Protocols and notes
    Hands the message off to another channel in the same project.
    Cloud
    Coming soon (engine-supported)

Standards

The formats a hospital network actually carries.

HL7 v2

MLLP and raw TCP framing, ACK/NACK, segment-level access in TypeScript.

FHIR R4 / R4B

Server listener, scheduled poll, and R4B subscriptions.

CDA / CCDA

Clinical document parsing and generation, with a document viewer.

X12

EDI transaction sets for eligibility, claims and remittance workflows.

DICOM

C-STORE SCP and SCU for imaging instance transfer.

IHE ITI

XDS.b ITI-41/42/43 document sharing, PIX ITI-8/9, PDQ ITI-21/22.

Direct

Direct secure messaging for provider-to-provider exchange.

SOAP

SOAP 1.1/1.2 services on both the receiving and sending side.

Raw / JSON / XML / CSV / binary

Everything else that shows up on a hospital network.

Transport & auth

How connections are secured.

  • TLS 1.2 or higher on every network listener and destination
  • Mutual TLS (mTLS) where the counterparty requires client certificates
  • Basic, bearer token, API key, OAuth2 client credentials, and SASL mechanisms
  • SSH private-key authentication for SFTP
  • Secret references resolved at runtime — never rendered into logs or traces

Gateway addresses

Cloud listeners are reachable at *.gw.intucloud.ai over TLS 1.2 or higher, on a shared address pool or on dedicated ingress and egress addresses as an add-on. Production listeners require an inbound allowlist.

Start building today.

Free plan, no credit card — design and test unlimited channels.