FAQs
Last updated
Was this helpful?
Last updated
Was this helpful?
In the fastn platform, flows are sequences of steps that perform an end-to-end operations like inserting data into a database or retrieving a list of products from a Shopify store.
Users can build flows to create APIs that give a synchronous real-time response or workflows that are executed as asynchronous jobs.
Using a range of available actions such as connectors, loops, switches, custom code, and more, users can tailor flows for their unique applications.
After a flow is created it can be run using the available Debugger which allows users to test the DRAFT version of the flow, see the output and debug any issues.
To run the Debugger, users can click on the Run Debugger button on the top right of the canvas page.
Once flows are tested and finalized, they can be deployed as the LIVE version. Users can use the Embed this Flow feature on the canvas page to generate code or curl commands that trigger the flow externally either as part of user applications or through API tools such as Postman.
API keys can be generated with desired permissions to authenticate access to selective flows.
Executed flows can be monitored in the Logs page which can be accessed using the navigation menu.
A flow can be tested at any stage during its creation using the Debugger.
To run the Debugger, users can click on the Run Debugger button on the top right of the canvas page.
The Debugger allows users to view the end result of a flow as well as any error messages that may have been thrown in the execution of the flow.
The step which threw the error is highlighted with a red border in the canvas page.
The Debug view in the Debugger can offer more insight by showing users the output of each step used in the flow.
When staged versions of flows are triggered externally using an API request, their logs and metrics are available in the Logs page.
For each flow, the executed steps are highlighted along with any steps that threw an error.
Using information gathered from these various means users can pinpoint the source of the error.
Once flows are tested and finalized, they can be deployed as the LIVE version. Users can then use the Embed this Flow feature on the canvas page to generate code or curl commands that trigger the flow externally.
The Generate API Key option can be used generate a new API key that is passed in the request headers to authenticate access to flows.
The generated code in the Embed This Flow dialog box can then be copied into a user application in the desired format.