Support for Server-Sent Events (SSE) with Custom Headers

Feature Requests Nodes
1

I would like to request the addition of support for Server-Sent Events (SSE) with custom headers in n8n. This feature would enable more dynamic and real-time interactions between n8n workflows and external services that utilize SSE.

Use Case: Many modern web services use Server-Sent Events (SSE) to push real-time updates to clients. By supporting SSE with custom headers, n8n can better integrate with these services, providing real-time updates and improving the responsiveness of workflows.

Proposed Solution:

Custom Headers: Allow users to specify custom headers when setting up the SSE connection. This is crucial for authentication and other custom header requirements of many SSE endpoints.

Customization: Allowing custom headers ensures that users can connect to a wider variety of SSE endpoints, including those requiring authentication.

Example Scenario: A user wants to monitor real-time stock prices from a financial service that provides SSE endpoints. By setting up an SSE node in n8n with the necessary authentication headers, the user can receive price updates in real-time and trigger workflows based on these updates, such as sending alerts or updating a database.

I believe that adding this feature would significantly enhance n8n’s capabilities and provide users with more flexibility and power in their workflows. Thank you for considering this request.

2

I’d like the ability to add Authorization to an SSE Trigger Node, just as is possible with the MCP Client Node.

3

I’m testing out n8n-nodes-sse-trigger-extended. Allows for standard bearer auth and header credentials as well as custom headers. Let me know if it works for you.