Load FASTA¶
Loads a FASTA sequence string into the workflow. It accepts multiline text and passes it through unchanged as a FASTA-typed output. No validation or parsing is performed; the node simply outputs exactly what you provide.

Usage¶
Use this node at the start of a biotech workflow when you already have a FASTA sequence (or multiple records) and need to provide it to downstream nodes for tasks like sequence analysis, structure prediction, or conversion. Paste or programmatically supply the FASTA text, then connect the output to nodes that consume FASTA.
Inputs¶
| Field | Required | Type | Description | Example | 
|---|---|---|---|---|
| fasta_string | True | STRING | The FASTA content to upload. Can include one or multiple FASTA records, with standard '>' headers and sequence lines. Content is not validated or reformatted. | >seq1 MGSSHHHHHHSSGLVPRGSHMASMTGGQQMGRGSEF-EXAMPLE >seq2 GATTACAGATTACAGATTACA | 
Outputs¶
| Field | Type | Description | Example | 
|---|---|---|---|
| sequence.fasta | FASTA | The provided FASTA content, passed through unchanged as a FASTA-typed value. | >my_protein MKTAYIAKQRQISFVKSHFSRQDILD-EXAMPLE | 
Important Notes¶
- This node performs no format validation; ensure your input follows FASTA conventions (header lines start with '>' followed by sequence lines).
- Outputs exactly the input text (including headers, line wrapping, and whitespace). Downstream behavior depends on the correctness of your FASTA.
- Supports multiple FASTA records in a single input string.
- Large inputs are accepted as plain text; consider memory limits if supplying very large multi-record FASTA files.
Troubleshooting¶
- If downstream nodes fail, verify headers and sequences are valid FASTA (no illegal characters, proper '>' headers).
- If the output appears empty, ensure the input field is filled and not just whitespace.
- If line wrapping causes issues in other tools, reformat your FASTA before loading (this node will not modify wrapping).
- If sequences map incorrectly downstream, confirm that record IDs in headers match the expectations of those nodes.