Nodes Overview
Nodes are the building blocks of every workflow in DotPortion. Each node performs a single, focused responsibility, and workflows are created by connecting nodes together in sequence.This approach makes backend logic visual, predictable, and easy to maintain. This page gives you a high-level overview of all nodes available in DotPortion.
Click on any node to view its detailed documentation.
How Nodes Work Together
A typical workflow looks like this:- Execution flows top to bottom
- Data flows between nodes
- The workflow ends when an API Response Node is executed
Core Nodes
πΉ API Start Node
Entry point of every workflow Defines how an HTTP request enters DotPortion.- HTTP Method
- URL Path
- Request entry
πΉ API Response Node
Ends the workflow and sends the response Controls the final HTTP status and response body.- Status codes
- Response output
- Terminates execution
Input & Validation Nodes
πΉ Request Parameters Node
Extract and validate incoming request data Used to define what input your API expects.- Body
- Query
- Headers
- Path params
Logic & Flow Control Nodes
πΉ Condition Node
Control execution using conditions Allows workflows to branch based on JavaScript expressions.- Boolean conditions
- Access dynamic values
- Guard logic
πΉ Logic Node
Write custom JavaScript / TypeScript Used when visual configuration is not enough.- Transform data
- Perform calculations
- Build objects
πΉ Loop Node
Iterate over lists Executes connected nodes for each item in an array.- Sequential execution
- Access current item
- Bulk operations
Authentication & Security Nodes
πΉ JWT Generate Node
Generate JSON Web Tokens Used for authentication and session handling.- Custom payload
- Token expiration
- Platform-managed secret
πΉ JWT Verify Node
Verify and decode JWTs Protects APIs by validating tokens.- Signature verification
- Expiration checks
- Payload decoding
Database Nodes
πΉ Database Node (Managed)
DotPortionβs built-in database No setup required. Ideal for MVPs and rapid development.- CRUD operations
- Managed MongoDB
- Project-scoped data
πΉ MongoDB Node (External)
Connect your own MongoDB database Used when working with existing or external databases.- Requires MongoDB connection URL
- Full CRUD support
- External data access
Choosing the Right Nodes
| Goal | Recommended Nodes |
|---|---|
| Build an API | API Start β Response |
| Validate input | Request Parameters |
| Apply logic | Condition / Logic |
| Process arrays | Loop |
| Store data | Database / MongoDB |
| Secure APIs | JWT Verify |
| Generate tokens | JWT Generate |
Best Practices
- Start every workflow with API Start
- End every API workflow with API Response
- Validate inputs early
- Keep logic nodes focused
- Prefer managed Database Node for quick builds
- Use MongoDB Node for existing databases
Whatβs Next?
- Learn how each node works in detail
- Build complete API examples
- Combine nodes to create real-world workflows