Start here
Core concepts
Workflows, nodes, runs, workspaces, teams and resources in one page.
| Concept | Meaning |
|---|---|
| Workflow | A saved pipeline: nodes and the lines between them. Versioned. |
| Node | One step: fetch, convert, extract, store, show. Thirteen registered types. See Nodes. |
| Run | One execution of a workflow (or one branch). Saved workflow runs are recorded and can be reopened. |
| Playground | An unsaved canvas for experiments. |
| Workspace | A folder of saved workflows you can share with a team. |
| Team | People who share workspaces and resources by invitation. |
| Resource | An authorized model endpoint or store; platform resources are included with the account. |
| Pattern | A glob such as */company?id=* that decides which links are followed. See Link patterns. |
How data flows
Section titled “How data flows”Each node passes its output to the nodes it is connected to. Pages go from the fetcher to the Markdown converter; Markdown goes to the LLM; records go to a Table and a Data Source. A node can feed several nodes, so one branch can store while another displays.
Inspect node outputs through the saved run. Output availability depends on the server’s retention and storage; a canvas is a reusable process, not a permanent archive of every intermediate artifact.
Composition and reuse
Section titled “Composition and reuse”Save a workflow to run it again. Use For Each to apply an inline graph to each upstream record, Combine to merge branches by key, and Query to read earlier stored results. These mechanisms serve different kinds of reuse.