What happens if my event fails schema validation?

The event is rejected and not written to the stream. No downstream consumers receive it. Fix the payload or disable schema validation, then republish.

Does publishing immediately guarantee the consumer sees it immediately?

If the consumer is an On Event trigger, the automation fires as soon as the event is written. Polling consumers (Consume Events, On Event polling) receive it on their next poll cycle.

Can I publish to multiple streams in one step?

No. Each Publish Event action targets one stream. Add multiple Publish Event steps to write to more than one stream in the same run.

Publish Event sends an event to a named stream immediately, after a set delay, or at a specific scheduled time. Events are validated against the stream's schema before they are written. Use it to fan work out to consumers, buffer request spikes, and connect producers to downstream automations without calling them directly.

Overview

The Publish Event action is the producer side of the Streams node. It places an event on a durable, topic-style stream where one or more consumers — polling or triggered — can read it. You supply a key that controls ordering: all events sharing the same key arrive in the order they were published; events with different keys may be processed in parallel and out of order relative to each other.

Input

Field	Type	Required	Description
Stream	String	Yes	Name of the target stream to publish to.
Key	String	No	Partition key for ordering. Events sharing the same key are kept in sequence. Events with different keys may be interleaved.
Payload	Object	Yes	The event data to write. Validated against the stream's schema by default.
Schedule type	Enum	Yes	When to publish: Immediately, After delay, or At specific time.
Delay duration	Number	Conditional	How long to wait before publishing. Required when Schedule type is After delay.
Delay unit	Enum	Conditional	Unit for the delay: Seconds, Minutes, Hours, or Days. Required when Schedule type is After delay.
Scheduled time	Timestamp	Conditional	The exact date and time to publish. Required when Schedule type is At specific time.
Skip schema validation	Boolean	No	When enabled, publishes without validating the payload against the stream's schema. Default: off.

Output

The action returns a confirmation once the event is accepted by the stream.

Field	Type	Description
eventId	String	Unique identifier assigned to the published event.
status	String	Confirmation that the event was accepted by the stream.

Notes

Published events are validated against the stream's schema by default. Disable validation only when you are certain the payload is already correct.
Ordering is per key — events with the same key arrive in sequence; events with different keys may be interleaved or processed in parallel.
Delivery is at-least-once. An event can arrive at a consumer more than once after a retry or an uncommitted offset, so make consumers idempotent.
Publishing with At specific time schedules downstream work without needing a separate Delay node in the workflow.
Each Publish Event step targets a single stream. Add multiple steps to write to more than one stream in the same automation.