Pause flow execution until a specific event is raised, enabling synchronization with external actions or other parts of the flow
The Wait For Event Block pauses the execution of a flow until a specific event is raised by a Raise Event Block or the host project. This block is crucial for scenarios where you need to synchronize your flow with external actions or other parts of the flow.
The name of the event to wait for. This input is only available if Use Event Name Input
is enabled in the settings. The value will be coerced to a string.
Any data to be passed through the block. This data will be outputted from the Data
output port. Optional.
The data passed in through the Data
input port, passed through unchanged. If no data was provided to the input, this output will not be available.
The data associated with the event that was raised. The type depends on what data was included when the event was raised. If the event has no associated data, this output will not be available.
The name of the event to wait for. Must match the name of the event raised by the Raise Event Block or the host project. Only used if Use Event Name Input
is disabled.
If enabled, the Event Name can be provided via the Event Name input port instead of being set in the settings.
Event Name
to myEvent
.Event Name
to myEvent
.myEvent
.The Wait For Event Block does not generate errors under normal circumstances. If the expected event is not raised, the block will wait indefinitely.
Can I use the Wait For Event Block to wait for multiple events?
No, each Wait For Event Block can only wait for a single event. To wait for multiple events, use multiple Wait For Event Blocks.
Can I use the Wait For Event Block with API calls?
Yes, you can use an HTTP Call Block to make an API call, then use the Wait For Event Block to wait for an event raised in response to that call.
Pause flow execution until a specific event is raised, enabling synchronization with external actions or other parts of the flow
The Wait For Event Block pauses the execution of a flow until a specific event is raised by a Raise Event Block or the host project. This block is crucial for scenarios where you need to synchronize your flow with external actions or other parts of the flow.
The name of the event to wait for. This input is only available if Use Event Name Input
is enabled in the settings. The value will be coerced to a string.
Any data to be passed through the block. This data will be outputted from the Data
output port. Optional.
The data passed in through the Data
input port, passed through unchanged. If no data was provided to the input, this output will not be available.
The data associated with the event that was raised. The type depends on what data was included when the event was raised. If the event has no associated data, this output will not be available.
The name of the event to wait for. Must match the name of the event raised by the Raise Event Block or the host project. Only used if Use Event Name Input
is disabled.
If enabled, the Event Name can be provided via the Event Name input port instead of being set in the settings.
Event Name
to myEvent
.Event Name
to myEvent
.myEvent
.The Wait For Event Block does not generate errors under normal circumstances. If the expected event is not raised, the block will wait indefinitely.
Can I use the Wait For Event Block to wait for multiple events?
No, each Wait For Event Block can only wait for a single event. To wait for multiple events, use multiple Wait For Event Blocks.
Can I use the Wait For Event Block with API calls?
Yes, you can use an HTTP Call Block to make an API call, then use the Wait For Event Block to wait for an event raised in response to that call.