SSE Trigger for KPN Streaming API icon

SSE Trigger for KPN Streaming API

Triggers the workflow when Server-Sent Events occur with support for custom headers

SSE Trigger for KPN Streaming API

AI-generated

Summary

Listen for Server-Sent Events (SSE) from a specified KPN Streaming API endpoint with optional custom headers and automatic OAuth2 token refresh, emitting each event's data as workflow output and optionally logging events to a selected data table.

Inputs

  • SSE Endpoint (required) — URL of the Server-Sent Events endpoint to connect to.
  • Group-Id-Suffix (required) — Identifier suffix for the consumer instance connecting to the SSE stream.
  • Data Table Logging (required) — Option to log incoming events into a data table ('With Logging' or 'Without Logging').
  • Credentials — Credentials for the KPN Streaming API used when logging is enabled or disabled.
  • Data Table — Data table to log events into, required if logging is enabled.
  • Event Column — Column in the data table to store the event type.
  • Data Column — Column in the data table to store the event data.
  • ID Column — Column in the data table to store the event ID.
  • Send Custom Headers — Boolean to determine whether to send additional custom headers with the SSE connection.
  • Specify Headers — Method to specify headers if sending custom headers: key-value pairs or JSON object.
  • Header Parameters — Key-value header parameters to send if using keypair header specification.
  • Headers (JSON) — JSON object of headers to send if using JSON header specification.
  • Connection Timeout (ms) — Maximum time to wait for the SSE connection before aborting (default 30000 ms).
  • Retry Attempts — Number of retry attempts to reconnect on failure (default 3).
  • Retry Delay (ms) — Delay between retry attempts in milliseconds (default 1000 ms).

Output shape

Workflow executions are triggered on each received SSE event, outputting an array with the event data and metadata.

If data table logging is enabled, events except 'ping' are also recorded in the selected data table with configured columns. The trigger automatically handles OAuth2 token refresh and will retry on connection failure up to configured limits.

Links

Discussion