Byteline offers a platform to develop a no-code backend solution. This document explains the basic concepts of flow, connection, trigger nodes, and task nodes to build your backend APIs or automation.
With the help of the Byteline flow designer, a user can create an end-to-end flow design consisting of trigger nodes and task nodes. A chain of the connected nodes that accomplish a particular functionality is called a flow. For more detail read: How to Create your first flow. Below is a simple example with two nodes.
Every flow is initialized with a trigger node, which can be one of HTTP API Trigger, Scheduler, or Form Submission Trigger. The trigger node is always the first node, and specifies how the flow is triggered or started.
Check out this documentation to understand each type of trigger node.
Once a flow is initialized with a trigger node, subsequent task nodes are added to the flow to design an API. Byteline supports a number of task nodes and the new nodes are added frequently. To check the documentation for task nodes, check Node Configuration category at https://docs.byteline.io/.
Nodes are added by using the + button on the last node of a flow. The below screen is then presented to pick the new node.
In the flow designer, the nodes are connected through connections. Whenever the user adds a new node to the flow a connection is built in-between the nodes. The below screenshot shows a connection line for a simple flow.