Thanks! Flyde is "just" a library behind the scenes, so you grab your .flyde file, and can run it with an npm package. For example:

``` import { loadFlow } from "@flyde/runtime";

const execute = await loadFlow("./celsius-to-fahrenheit.flyde");

const inputs = { celsius: 0 }; // "celcius" is a main input in the flow, therefore it must be provided when executing the flow const { result } = execute(inputs); // execute returns a "result" promise, along with a cleanup function that can be used to cancel the execution.

const { fahrenheit } = await result; // each output in the flow is a property on the result object

console.log(fahrenheit) ```

(taken from https://www.flyde.dev/docs/integrate-flows/)

But your comment strengthens my feeling that making this more intuitive and discoverable and is indeed something I should prioritize

Nice! I definitely will try it :)