Importing Examples
Subfork graph imports replace the graph currently loaded in the editor. Create a new graph first if the current graph contains work you want to keep.
- Open the example’s
*.notes.mdfile and review its requirements. - Download the adjacent
*.subfork.jsonfile. - In Subfork, create or open the destination graph.
- Open Graph Settings, select Import, and choose the JSON file.
- Inspect the graph before running it. In particular, review HTTP destinations, exposed responses, and provider-backed nodes.
- Configure any documented execution-profile variables or secrets.
- Save the imported graph, run it, and inspect its panels and outputs.
Trust And Secrets
Graph JSON is executable configuration. Only import files you trust, and review network requests and scripts just as you would review source code.
Exports must not contain secret values. Examples refer to secrets by stable names
such as OPENAI_API_KEY; add the actual value in the destination graph’s
execution profile. Never paste a key into a Value, Template, URL, or script node.
Compatibility
Examples currently use the subfork.graph/1 export format. If an import fails,
update Subfork first and check the example’s recent history. A successful import
does not guarantee that external providers or public datasets are currently
available.