Node Reference¶
SchemAlign nodes are the building blocks used on the Workspace canvas to move data through an integration. This section is the documentation home for node behavior, configuration guidance, and node-specific reference pages.
Nodes are organized by the role they play in a pipeline:
Source nodes¶
Source nodes bring data into a pipeline from an external system, file, API, or inbound request.
Compose nodes¶
Compose nodes prepare data after it enters the pipeline. This is where SQL-centered loading and transformation patterns live.
Destination nodes¶
Destination nodes write, send, return, or publish pipeline results after the source and compose steps are complete.
Current node catalog¶
| Category | Node | Purpose |
|---|---|---|
| Source | HTTP Get | Call an HTTP endpoint and use the response as pipeline input. |
| Source | Ethos Get | Retrieve and load records from an Ethos Integration API endpoint. |
| Source | File Get | Retrieve an input file for downstream loading or transformation. |
| Source | Inbound HTTP Request | Start or feed a pipeline from an inbound HTTP request payload. |
| Compose | SQL Loader | Load source stream data into SQL-accessible working data. |
| Compose | SQL Transform | Transform, shape, filter, or join data using SQL-centered logic. |
| Destination | File Put | Write an upstream stream or artifact to an SFTP destination. |
| Destination | HTTP Response | Define the response returned to an inbound HTTP caller after the pipeline completes. |
How to use this section¶
Use the category pages first when you are deciding which type of node belongs in a workflow. Each dedicated node page follows the same reference pattern:
- a short description near the top
- a field reference table with each configuration field and description
- usage patterns
- inputs and outputs
- validation and common errors
- security or credential considerations
Node documentation buildout
This section establishes the stable documentation location for SchemAlign nodes. Dedicated node pages are being expanded one node at a time, including File Put and HTTP Response.