Skip to content

Processors reference

EIP (Enterprise Integration Pattern) processors operate on the Exchange between route steps. Helix groups them by file under pkg/processor/; one reference page per file.

Source files

bin/audit-docs --category processors is the source of truth. Per-file pages document every constructor and every public parameter.

The audit currently expects:

aggregate, choice, convert, dataformat, eip, eip_advanced, eip_extra, error_handling, filter, idempotent_redis, loop_dynamic, multicast, normalize, on_completion, pipeline, poll_enrich, read_file, remove_headers, resequencer, resilience, routing, split, step, streaming_json, transform.

Conventions

  • Each page leads with the Go constructor signature and the YAML form.
  • Each parameter has a one-line description, type, default, and whether it's required.
  • Each page ends with at least one runnable example validated by helix validate.

See also