Node-RED ⇄ Pulse
Node-RED owns the visual flow; Pulse is the stream-processing step it calls through its stock http request node — no custom node, no code. Repo example: examples/nodered-pulse-bridge/ — ran end-to-end on a real Node-RED 5.0.1 installed from npm.
[Inject] → [build order] → [http POST → Pulse] → [delay] → [http GET ← Pulse] → [decide] → [file]
Run it
pulse server start --dev
mkdir app && cp pulse.yaml app/ && (cd app && pulse deploy .) # stands up order-scoring
npm install node-red
PULSE_URL=http://localhost:9090 ./run_headless.sh
Or interactively: launch node-red, Import flows.json, set PULSE_URL / PULSE_TOKEN in the environment (the nodes read them via env.get(...)), hit Deploy — the start once Inject fires the flow.
Validated output
amount=2500 decision=escalate
amount=300 decision=auto-approve
Same contract as every bridge: POST the ingress, read the stage topic. Enrich the Pulse stage with windows, joins or an llm stage — the two http nodes never change.
Next
- n8n guide — the same pattern in the other big low-code tool
- Call your app from anywhere