Overview
This node implements a Server-Sent Events (SSE) client designed to receive real-time data streams from an MPC Server. It is useful in scenarios where continuous, event-driven updates are needed without repeatedly polling an API. For example, it can be used to listen for live updates on points or transactions in a loyalty program system, enabling workflows that react instantly to new data.
Properties
| Name | Meaning |
|---|---|
| SSE Endpoint | The URL of the SSE server endpoint to connect to for receiving event streams. |
| Authentication | The authentication method used to authorize the connection; currently supports Bearer Auth. |
| Tools to Include | Specifies whether to include all available tools or only selected ones in the data stream. |
Output
The node outputs JSON data representing the events received from the MPC Server via the SSE connection. Each output item corresponds to an event payload streamed from the server. The structure of the JSON depends on the specific event data sent by the MPC Server. There is no indication of binary data output.
Dependencies
- Requires a valid SSE endpoint URL.
- Requires an API authentication token using Bearer authentication.
- Needs network access to the specified SSE endpoint.
- No additional external libraries or services are indicated beyond standard SSE and HTTP authentication mechanisms.
Troubleshooting
- Connection failures: Ensure the SSE endpoint URL is correct and accessible from the n8n instance.
- Authentication errors: Verify that the provided Bearer token is valid and has necessary permissions.
- No data received: Confirm that the MPC Server is actively sending events and that the "Tools to Include" setting matches the expected data scope.
- Unexpected disconnections: Network instability or server-side issues may cause SSE disconnects; consider implementing reconnection logic if supported.