Streams by UnifyApps provides event streaming capabilities for automation workflows.

Overview

Streams by UnifyApps provides event streaming capabilities for automation workflows. The node enables reliable message passing between automation processes through a stream-based publish/subscribe model, supporting consumer groups, delayed delivery, and dead-letter queue management for resilient event-driven architectures.

Actions

Polls for New Events

Listens to a stream for new events and triggers the automation when new messages arrive. This action is typically used as or near the start of an automation to drive event-based processing.

Key Input Fields:

• Select Stream — The stream to poll

• Repeat — Whether the node continuously re-polls after processing each batch

• Consumer Group — Identifies a group of consumers that share processing of stream events; enables parallel processing and exactly-once delivery guarantees

• Batch Size — Number of events to retrieve per polling interval

Output: Event data payload, event metadata (key, timestamp, stream ID).

Publish Event to Stream

Immediately publishes an event to a stream for real-time downstream processing.

Key Input Fields:

• Stream — The target stream to publish to

• Key — Partition key that determines event ordering and routing within the stream

• Event data — The payload to include with the event

Output: Published event ID, stream acknowledgement, timestamp.

Publish Event to Stream At

Schedules an event for delivery at a specific point in time, enabling time-coordinated workflows and scheduled processing patterns.

Key Input Fields:

• Stream — Target stream

• Key — Partition key

• Time to publish at — ISO 8601 DateTime specifying the exact delivery time

• Event data — The event payload

Publish Event to Stream with Delay

Delays event delivery by a configured duration relative to the time of publishing, useful for retry strategies and time-delayed follow-up automations.

Key Input Fields:

• Stream — Target stream

• Key — Partition key

• Time delayed for — Numeric duration value for the delay

• Unit — Time unit (Seconds, Minutes, Hours, Days)

• Event data — The event payload

Update DLQ Status for Stream

Updates the processing status of an event that has been moved to the dead-letter queue (DLQ) after repeated failures, allowing manual review and resolution of problem events.

Key Input Fields:

• Stream — The stream containing the DLQ event

• Event Id — Unique identifier of the DLQ event to update

• DLQ Reason — Description of why the event failed, recorded for audit and troubleshooting

Note: Consumer groups ensure that each event is processed by only one consumer in the group, enabling horizontal scaling of event processing automations without duplicate processing.

Notes

Keep the following in mind when using Streams by UnifyApps:

• Events published to a stream are consumed in order; if strict ordering matters, publish events from a single automation rather than from concurrent runs.

• Check the dead-letter queue (DLQ) regularly when using Streams in production; failed events accumulate there and will not be retried automatically unless you use Update DLQ Status.

• Use Publish Event to Stream with Delay when you need a timed action without setting up a full Schedule trigger.

• Set the polling interval for Polls for New Events based on your latency requirements and the expected volume of events.

• Test end-to-end by publishing a test event and confirming the consuming automation receives and processes it before deploying to production.