Visual Canvas

The Visual Canvas is where you design the logic for your endpoints. Instead of writing lines of code, you connect functional blocks (nodes) to create a flow that handles requests, processes data, and returns responses.

Key Functionalities

1. Node-Based Design

Build your logic by dragging and dropping nodes from the library (40 nodes in total). Each node represents a specific action. The main categories are:

Triggers: The entry point of your endpoint — one of four types: HTTP API, Webhook, Schedule, or Telegram/Twilio.
AI: The agent node (DYPAI Managed or your own BYOK key) and the image_generation node (managed-only, billed as AI Credits, returns a storage URL).
Database, Storage & Auth: Read/write your tables, manage files, and run server-side auth operations.
Logic & Control: Add conditions (if/else), loops, filters, merges, and field transformations.
Communication & Integrations: Connect ~24 third-party services like WhatsApp, Stripe, Slack, Telegram, Notion, GitHub, and more — or call anything else with the generic HTTP Request node.
Code node: The javascript_code node runs custom JavaScript with plaintext env_vars (ctx.env).

See the full Workflow Nodes & Integrations reference for every node by category.

2. Manual Testing

You have full control over your logic. Use the Test button to verify your flow. By running manual tests, you can:

Ensure all nodes are correctly connected.
Check that inputs and outputs match your expectations.
Identify any logic issues before deploying.

3. Integrated Testing Panel

The Testing Panel is your best friend for debugging.

Simulate Requests: Send test data to see how your flow responds.
Step-by-Step Execution: Watch how data moves through each node in real-time.
Logs: Review detailed execution logs to debug any issues.

4. AI Assistance (MCP)

You can use your AI assistant to modify the Canvas for you. Simply ask:

"Add a validation step to check if the user is an admin."
"Connect the database output to a new WhatsApp notification node."

Best Practices

Keep it Modular: Break complex logic into smaller, manageable flows.
Use Descriptive Names: Rename your nodes to reflect their specific purpose (e.g., "Fetch User Profile" instead of just "Query").
Test Frequently: Use the testing panel after adding new nodes to ensure everything is working correctly.

Key Functionalities

Build your logic by dragging and dropping nodes from the library (40 nodes in total). Each node represents a specific action. The main categories are:

Triggers: The entry point of your endpoint — one of four types: HTTP API, Webhook, Schedule, or Telegram/Twilio.

AI: The agent node (DYPAI Managed or your own BYOK key) and the image_generation node (managed-only, billed as AI Credits, returns a storage URL).

Database, Storage & Auth: Read/write your tables, manage files, and run server-side auth operations.

Logic & Control: Add conditions (if/else), loops, filters, merges, and field transformations.

Communication & Integrations: Connect ~24 third-party services like WhatsApp, Stripe, Slack, Telegram, Notion, GitHub, and more — or call anything else with the generic HTTP Request node.

Code node: The javascript_code node runs custom JavaScript with plaintext env_vars (ctx.env).

See the full Workflow Nodes & Integrations reference for every node by category.

You have full control over your logic. Use the Test button to verify your flow. By running manual tests, you can:

Ensure all nodes are correctly connected.

Check that inputs and outputs match your expectations.

Identify any logic issues before deploying.

The Testing Panel is your best friend for debugging.

Simulate Requests: Send test data to see how your flow responds.

Step-by-Step Execution: Watch how data moves through each node in real-time.

Logs: Review detailed execution logs to debug any issues.

You can use your AI assistant to modify the Canvas for you. Simply ask:

"Add a validation step to check if the user is an admin."

"Connect the database output to a new WhatsApp notification node."

Best Practices

Keep it Modular: Break complex logic into smaller, manageable flows.

Use Descriptive Names: Rename your nodes to reflect their specific purpose (e.g., "Fetch User Profile" instead of just "Query").

Test Frequently: Use the testing panel after adding new nodes to ensure everything is working correctly.