Flow Nodes vs. Client-Side Services Nodes: What's the Difference?

Community Best Practices & Tutorials
1

Hi Neutrinos Studio Community,
I’m currently learning Neutrinos Studio and have encountered a situation that’s causing some confusion. I’ve noticed that same nodes existing both within the Flow editor and the Client-Side Services section.
What are the key distinctions in how these nodes function when used in a Flow versus a Client-Side Service ?
Any insights or explanations would be greatly appreciated. Thank you!

2

@ragesh-a @Muhseena_T please help

3

Flow Nodes vs. Client-Side Service Nodes: What’s the Difference?

Nodes in Neutrinos Studio are reusable logic units that perform specific tasks. Their behavior depends on the parameters provided. For example, the HttpIn node listens for incoming requests based on the specified METHOD and PATH—making it essential for API applications but unnecessary for UI applications.

The key distinction lies in where and how these nodes are used:

  • Flow Nodes are typically used in API applications to define server-side logic.
  • Client-Side Service Nodes are utilized in UI applications to handle client-side processes.

Nodes That Differ Between UI and API Apps

Some nodes are exclusive to either UI or API applications:

  • API-specific nodes (e.g., HttpIn) process incoming API requests and are not needed in UI apps.
  • UI-specific nodes (e.g., UI components) help build user interfaces but have no role in API apps.

Nodes That Work in Both

Certain nodes, like the Script node, can be used in both UI and API applications to execute custom logic.

For example, consider a calculator application:

  • On the UI side, the Script node can define how calculations are performed directly in the client.
  • On the API side, the same Script node can process calculations server-side when parameters are sent via API.
4 Likes