Hey Bubblers! 
I’m excited to share a plugin I’ve been building for a while: **W4B (Workflow For Bubble)** — a visual automation engine that lets you design, test, and execute complex business logic directly in Bubble, without writing backend code.
What is it?
W4B gives you a drag-and-drop canvas to build flows using a library of 40+ nodes. You connect nodes, inject dynamic variables, call APIs, and run the whole thing directly from a Bubble workflow — client-side or server-side.
Think of it as a visual logic layer that sits between your Bubble data and your workflows.
What can you do with it?
Control flow
Conditions (IF/ELSE), Switch/Case, Loop/ForEach, Delay, Stop — build any branching logic visually.
Call APIs
Hit any external endpoint with full control over method, headers, params, and body. Use dynamic variables in any field.
Bubble-native operations
Get Thing, Get List, Create, Update, Replace, Delete, Bulk Create, and Run API Workflow — all as dedicated nodes, pre-configured for the Bubble Data API.
Transform data
Remap objects, parse JSON, filter/sort/map/group arrays, run math operations, format numbers and dates, encode/decode strings.
Run from anywhere
Use the Run Flow (Client) or Run Flow (Server) action in any Bubble workflow. Pass a payload, a global context, and get back the full output as JSON.
Dynamic variables
Reference any value anywhere using {{payload.field}}, {{context.key}}, {{result.data}}, {{loop.index}}, or any variable you saved mid-flow.
How it works
1. Add the element to a dedicated page
2. Build your flow in the canvas
3. Save — the encrypted flow is stored in a state you bind to your database
4. Trigger it from any workflow with Run Flow (Client) or Run Flow (Server)
5. Get back success, output_json, logs_json, error_message
Template library
The element comes with a built-in template library — click the button in the header to browse ready-made flows and get started faster.
Plugin page: [link]
Live demo: https://w4b.bubbleapps.io/version-test
Demo editor: w4b | Bubble Editor
Happy to answer any questions — feedback very welcome! 
Create a new flow — just a name and you’re in the editor.
Open the API Connector — the built-in integration manager where you register your endpoints once and reuse them as drag-and-drop nodes.
Register a GET endpoint — we’ll use JSONPlaceholder (a free public API) as an example:
Test the connection — one click, instant 200 OK with the full JSON response right there in the editor. You see exactly what the API returns before you even build your flow.
This step isn’t optional — just like Bubble’s API Connector, W4B requires the endpoint to be initialized with a successful 200 response before it can be used as a node. No green light, no node on the canvas. This guarantees that every integration you drag into a flow is already proven to work.
Drop it on the canvas — once initialized, “JSONPlaceholder → Get User” appears as a node in the sidebar. Drag it in, connect it to Start.
Set up the payload — in the Start node, add a key called “id” with the value 2. Then in the Get User integration node, use {{payload.id}} to dynamically resolve the [id] parameter in the URL. This is how you pass data from the trigger into any API call.
Add two Log nodes — one for Success and one for Error. In the integration node, save the API response to a variable called “result”. Then wire both log nodes:
First run — hit Run, the flow calls GET /users/2, and the Success log shows the full JSON for user 
Change the payload and run again — go back to the Start node, change the id from 2 to 3, and hit Run again. Now the log shows a completely different user (
Register once, use everywhere — change a base URL or header in one place, every node updates