Flow control
- Conditions
- If/else branches and comparisons.
- Loops
- Collections, ranges, and while loops.
- Variables & logs
- Keep values and trace your flow.
Define API inputs and responses, connect reusable logic nodes, and control each request with conditions, validation, authentication, and error handling.
Scroll to explore the flow
Two separate visual previews. Requests are arranged under Orders and Customers group lines. The order logic flow has grouped Body and Header inputs, a reusable custom node to validate and prepare the order, an inventory API call using ENV.STOCK_KEY, and a database action. Each result connects to a field in the Outputs group: the order with HTTP 201, invalid input with 422, or an unavailable inventory service with 502.
Orders and Customers endpoints are shown with their typed inputs and responses. The other tabs show the logic behind POST /orders.
Use built-in actions for everyday backend work, then extend them with your own nodes.
Turn your own functions into a configurable block. Define the form, add the implementation, and reuse it across your backend.
Typed fields, defaults, variants, and conditional options.
Connect the configuration to your own implementation.
Use it across requests or publish a node template.
Connect payments, email, AI, and more through custom nodes and API calls. Keep credentials in workspace variables.
Accept payments, manage subscriptions, and handle checkout events in your flows.
Send welcome emails, receipts, and account notifications from your backend.
Add AI responses, summarization, and structured extraction to your requests.
Analyze documents, work with long context, and build AI-powered workflows.
Send SMS alerts, verification codes, and WhatsApp messages from your flows.
Send team alerts, approval requests, and workflow updates to your channels.
Upload files, store assets, and generate signed URLs for controlled access.
Use authentication, Firestore, and push notifications alongside your backend.
Create issues, trigger workflows, and connect repository events to your backend.
Make permissions, validation, and failure paths part of your backend design.
/ordersRequire authentication and choose which roles can call each endpoint.
Reference workspace variables across your API calls without hardcoding keys.
201401403409422502Give failures their own paths, response bodies, and HTTP status codes.
STOCK_KEYCatch missing values, unlinked inputs, and configuration issues as you build.