Flow Designer Node Reference
This page documents nodes currently available in the Flow Designer frontend palette definitions. Use it as a practical catalog when designing routes visually or generating compatible YAML from automation.
1. Designer model
Node categories and counts in this documentation snapshot:
- Sources: 11
- Processors: 16
- Control Flow: 7
- Sinks/Destinations: 9
Total documented: 43 nodes
Counts are based on the Flow Designer palette snapshot and should be verified against the console UI build used in your release.
Palette search matches label, description, and tags. Unsupported constructs imported from YAML may appear as custom nodes.
2. Full node catalog
| Category | Type | Label | Purpose |
|---|---|---|---|
| Source | timer | Timer Inbound | Generate messages at scheduled intervals |
| Source | httpInbound | HTTP Inbound | Expose inbound HTTP endpoint with optional method restrictions |
| Source | tcpInbound | TCP Inbound | Listen for inbound TCP payloads with line or raw framing |
| Source | file | File Inbound | Poll a directory for new files |
| Source | jms | JMS Consume | Consume messages from a JMS queue or topic |
| Source | direct | Direct Inbound | Synchronous in-memory endpoint for route composition |
| Source | kafka | Kafka Consume | Consume messages from Kafka topic |
| Source | sse | SSE Consume | Consume server-sent events (SSE) from an HTTP stream |
| Source | websocket | WebSocket Consume | Consume messages from a WebSocket stream |
| Source | soap | SOAP Inbound | Expose a SOAP web service endpoint |
| Source | fileTransferSource | Remote File Inbound | Poll files from FTP or SFTP endpoints |
| Processor | dbQuery | DB Query | Execute SQL against a database (read/write/stream) |
| Processor | delimitedParser | Delimited Parse | Parse delimited key/value text into map/body/header/property |
| Processor | log | Log | Log message content and headers |
| Processor | setBody | Set Body | Replace message body with a new value |
| Processor | setHeader | Set Header | Set or modify a message header |
| Processor | setProperty | Set Property | Set or modify an exchange property |
| Processor | transform | Transform | Open Data Mapper for visual data transformation |
| Processor | bean | Bean | Call a method on a Spring bean |
| Processor | delay | Delay | Delay message processing by configured duration |
| Processor | filter | Filter | Filter messages based on a condition |
| Processor | enrich | Enrich | Enrich message with data from external source |
| Processor | marshal | Marshal | Convert data to target format (JSON/XML/CSV) |
| Processor | unmarshal | Unmarshal | Parse data from serialized format |
| Processor | script | Script | Execute a script (Groovy, JavaScript, etc.) |
| Processor | custom | Custom Step | Paste raw Camel YAML for advanced processor behavior |
| Processor | validate | Validate | Validate message content against a predicate |
| Control | choice | Choice | Content-based routing (if/else) |
| Control | split | Split | Split a message into multiple parts |
| Control | aggregate | Aggregate | Combine multiple messages into one |
| Control | multicast | Multicast | Send same message to multiple branches in parallel |
| Control | loop | Loop | Repeat processing a configured number of times |
| Control | dynamicRouting | Dynamic Routing | Route to dynamically resolved endpoint lists at runtime |
| Control | doTry | Try/Catch | Handle exceptions with try/catch/finally branches |
| Sink | httpRequest | HTTP Send | Send HTTP request with headers/auth/body options |
| Sink | sendTo | Generic Endpoint (Advanced) | Advanced sender for static or dynamic Camel URIs |
| Sink | emailSink | Email Send | Send outbound email over SMTP/SMTPS |
| Sink | jmsSink | JMS Send | Publish message to JMS queue/topic |
| Sink | fileSink | File Write | Write messages to files in a directory |
| Sink | kafkaSink | Kafka Send | Publish messages to Kafka topic |
| Sink | wireTap | Wire Tap Send | Send a copy of the message to another endpoint |
| Sink | fileTransferSink | Remote File Upload | Upload files over FTP or SFTP |
| Sink | soapSink | SOAP Send | Call an outbound SOAP endpoint using CXF |
3. Recommended node composition patterns
Pattern A: API ingress with async handoff
HTTP Inbound -> Validate -> Transform -> JMS SendPattern B: Fan-out orchestration
Timer Inbound -> Multicast -> (HTTP Send + DB Query + File Write) -> AggregatePattern C: Resilient integration
Source -> Try/Catch -> (business processors) -> Sink
\-> error sink (dead letter)4. Import/export and runtime notes
- Flow Designer is optimized for single-route documents.
- Complex unsupported DSL constructs can be preserved as custom nodes.
- Generated routes should still be validated against ingress/path and route ID rules before deployment.
- Use management API route content endpoints for round-trip edit workflows.
Schema reference: buzen-flow-designer-route.schema.json