Skip to main content

Working with Data Connectors: JSON Streaming Push

The Data Connector JSON Streaming Push allows you to push real-time information through a WebSocket (network protocol based on TCP that establishes how data should be exchanged between networks).

Please note that for incoming streaming WebSocket connections, we accept messages up to 65KB in size. If your integration requires handling payloads larger than this limit, please use a plain JSON and the HTTP Push Data Connector instead. For more information about the HTTP push data connector, please click here.


Requirements

Generate Data connectors Inputs and configure as JSON Streaming Push - Content


Generate the Data Connector Input

(1) unfold the Settings at the top menu and then select Data Connectors - Inputs. (2) Click on Add and choose JSON Streaming Push - Content.

(3) Edit the new Input.

(4) The token is the identifier that is generated for each new Input. (5) Push URL is the instruction with the integrated token. (6) You can assign the name of your Input. (7) Schema is the section where you can edit the JSON schema.

Adding the Data Connector to the Graphics Editor

First, you need to add an External Connector to your tree (1) and then click on Connect (2).

From the External Source panel choose JSON Streaming Push (if it's not listed contact your designated Customer Success Manager).

Setting up the JSON Streaming Push

(1) Select the Input you created.

After adding the JSON´s Input, (2) check that the connection is available, selecting in the Inspector, View Source -> Event Stream. After these steps, you can start making your graphic.

Just to let you know, the payload of the Streaming outputs isn't durable. The connector remembers the last payload, but if the service restart the last payload will be lost. The best practice when using this connector is to stay connected and push the payload again on reconnect.

JSON streaming push example Graphics


How this connector works — unidirectional data flow

The JSON Streaming Push connector is unidirectional: your system sends data to Flowics through the WebSocket connection, but Flowics does not send any messages back to your client.

This means:

  • ✅ Your client establishes a WebSocket connection to the Flowics endpoint

  • ✅ Your client sends JSON payloads and Flowics receives them

  • ❌ Flowics does not send return packets or acknowledgements back to your client

If you are testing with a tool like WebSocketKing or wscat and not receiving any messages back, this is expected behavior — it does not mean the connector is broken or that your data is not being received.

To confirm your data is actually reaching Flowics, go to Settings → Data Connectors → Inputs, open your Data Input, and click View Source → Event Stream. The last payload you pushed will appear there.


Troubleshooting

I'm not receiving return packets in my WebSocket client

This is expected. The JSON Streaming Push connector does not send data back to your client. See the section above for how to verify your data is being received by Flowics.

The WebSocket connection is not establishing

  • Confirm the WebSocket URL is copied exactly from Settings → Data Connectors → Inputs → Push URL

  • Check that outbound ports 80 and 443 are open on your network

  • If you are behind a proxy or VPN, confirm that WebSocket traffic (wss://) is not being blocked — proxies often intercept and drop WebSocket upgrade requests

The connection establishes but the graphic is not updating

  • Go to Settings → Data Connectors → Inputs → open your Data Input → click View Source → Event Stream and confirm the latest payload is visible there

  • If the payload is visible in the Event Stream but the graphic is not updating, check that the Data Connector in the Graphics Editor is connected to the correct Data Input

  • Confirm the graphics package has been published after any schema or connector changes

  • Verify the JSON payload structure matches the schema defined in the Data Input

My payload is being rejected or the connection drops immediately

  • Check the payload size — messages over 65 KB are not accepted. If your payload exceeds this limit, switch to the JSON HTTP Push connector instead

Did this answer your question?