Source Nodes¶
Source nodes bring data into a SchemAlign pipeline. A source may read from an API, retrieve a file, or accept an inbound request that supplies the starting payload for the run.
Use source nodes at the beginning of a pipeline branch, then connect them to compose or destination nodes based on the workflow design.
Source node catalog¶
| Node | Use when | Common downstream path |
|---|---|---|
| HTTP Get | The pipeline needs to call an external HTTP endpoint and process the response. | HTTP Get -> SQL Loader or SQL Transform |
| Ethos Get | The pipeline needs to retrieve and load records from an Ethos Integration API endpoint. | Ethos Get -> SQL Transform |
| File Get | The pipeline needs to retrieve an input file before loading or transforming it. | File Get -> SQL Loader -> SQL Transform |
| Inbound HTTP Request | The pipeline starts from, or needs to respond to, an incoming HTTP request. | Inbound HTTP Request -> SQL Transform -> HTTP Response |
Choosing a source node¶
| Source node | Best fit |
|---|---|
| HTTP Get | General-purpose HTTP or HTTPS retrieval where the response should flow downstream as a stream, file-like packet, or optional artifact. |
| Ethos Get | Ethos-specific retrieval where records should be fetched with Ethos token handling, paged through, flattened, and loaded into derived tenant tables. |
| File Get | File retrieval before SQL loading, transformation, validation, or delivery. |
| Inbound HTTP Request | Request-driven workflows that begin from an incoming HTTP payload and may pair with an HTTP Response destination. |