Destination Nodes¶
Destination nodes complete a pipeline branch by writing, sending, returning, or publishing the result produced by source and compose nodes. Use destination nodes when the prepared output should leave the pipeline, be uploaded to a configured location, or be returned to an inbound HTTP caller.
Destination node catalog¶
| Node | Use when | Common pipeline pattern |
|---|---|---|
| File Put | The pipeline needs to upload an upstream stream or artifact to an SFTP destination. | SQL Transform -> File Put |
| HTTP Response | The pipeline needs to define the final response returned to an inbound HTTP caller. | Inbound HTTP Request -> SQL Transform -> HTTP Response |
Choosing a destination node¶
| Destination node | Best fit |
|---|---|
| File Put | File delivery over SFTP after a source or compose node has produced stream bytes or a published artifact. |
| HTTP Response | Request-driven workflows where the caller should receive JSON, XML, text, a file, no body, or a status response after the pipeline completes. |
Private-network routes¶
File Put can use an authorized SchemaDock to reach a private SFTP destination. HTTP Response does not use SchemaDock because it returns a response to an inbound caller rather than initiating an outbound private-network connection.
See SchemaDock Connection Routes.