Channel Destination

The Channel destination forwards processed messages to another channel within the same project, enabling multi-stage pipelines where one channel’s output feeds directly into the next channel’s input.

This is the building block for fan-out architectures — a single channel can route messages to multiple downstream channels, each with its own transformer, destinations, and retry policy.

Configuration

destination:
  type: channel
  channel:
    target_channel_id: fhir-converter

The target_channel_id must exactly match the id field of a downstream channel defined in the same project.

Properties

Property	Type	Required	Default	Description
`target_channel_id`	`string`	Yes	—	The `id` of the downstream channel to forward messages to. Must match an existing channel in the project.

Validation

Running intu validate checks all channel destination references and will reject the configuration if:

The target_channel_id does not match any channel in the project.
A circular reference is detected (e.g., channel A routes to channel B, which routes back to channel A).

Complete Example

An HL7v2 intake channel that fans out to three independent downstream channels:

id: hl7-intake
enabled: true
group: admissions

source:
  type: tcp
  port: 6661
  content_type: hl7v2
  mllp: true

transformer: normalize.ts

destinations:
  - type: channel
    channel:
      target_channel_id: fhir-converter

  - type: channel
    channel:
      target_channel_id: adt-analytics

  - type: channel
    channel:
      target_channel_id: patient-index

Each downstream channel operates independently — it has its own transformer, destinations, and retry policy. A failure in one branch does not affect the others.