Skip to content

Node reference

Nodes overview

Thirteen implemented node types, their purpose, and where to find their contracts.

NodeType idDoes
URL FetcherurlFetcherReads pages: one, several, or everything reachable within a depth
Markdown ConvertermarkdownConverterTurns pages into clean text
LLM ProcessorllmProcessorAnswers a question about the pages, or extracts one record from each
Data SourcedataSourceStores records (and optionally images)
MongoDB StoremongoStoreStores structured records, with optional derived keys
File storages3StoreStores referenced files and attaches blob references
For EachforEachExecutes an inline graph per upstream record
CombinecombineMerges branch records by key
QueryqueryReads stored data back
Data TransformerdataTransformerSelects or cleans HTML, or extracts JSON values
Table, Chart, Texttable chart textShow a result

Any node type can be a starting point of a workflow. Option names in the app and API are crawler-core’s, in snake_case; the canvas also accepts camelCase aliases.

Each guide explains inputs, outputs, usage, and failure behavior. The generated configuration tables list declared parameter types, defaults, enums, and bounds directly from engine contracts. MCP clients can call list_node_types(type) against their server to discover the deployed schema.