Appearance
Send streaming response
Stream event data back to the caller while your API Endpoint workflow runs. This is useful when you want to show progress for long tasks (like imports, file generation, or AI responses).
How it works
Instead of waiting until your workflow is finished, WeWeb can send updates as they happen.
Here’s what that means in practice:
- The first time
Send streaming responseruns, WeWeb starts a “live” response. - Each next
Send streaming responseadds another message to that same response. - Your app can read those messages and update the UI (for example show progress, or display new text as it arrives).
What “streaming” means
Streaming is just a way of keeping the connection open so WeWeb can send multiple updates. This uses a standard called Server‑Sent Events (SSE).
Configuration
| Setting | What it does |
|---|---|
Event Data | The data to send as the next message in the stream. |
Using the stream in your interface
To receive streaming messages in an interface workflow, you need to call your endpoint and enable stream handling:
- In
Interface, create a workflow (for example “On click”). - Click
+ Add an action, then go toWorkflows→APIand select your API Endpoint. - Open the action’s
Advancedsection and enableHandle stream. - Run the workflow.
While the workflow is running, you can use the streaming data in bindings from that action:
stream.chunk— The latest message receivedstream.chunks— All messages received so far
Example: stream progress updates
In your API Endpoint workflow, you can send progress messages as you go:
- Start your long task (for example, looping through rows to import)
- After each step, add
Send streaming responsewithEvent Datalike:{ "step": "import", "done": 5, "total": 20 }
- In your interface, bind
stream.chunkto a progress UI (like a text label or progress bar)
Common pitfalls
Nothing shows up in the interface
- Make sure you enabled
Handle streamon the API Endpoint action you added fromWorkflows→API. - Make sure your API Endpoint workflow actually runs
Send streaming responseat least once.
CONTINUE LEARNING
Learn how to call endpoints from your interface workflows.

