Callback
The Callback node lets you add a pause to the workflow execution. The flow execution resume when the callback is received, such as. a REST API call from a 3rd party system. The input parameters for the Callback Node are:
Callback ID
An unique string identifier to represent this flow execution(so callback will only resume this flow execution), it could be a global(tenant level) unique Id that generated by current flow execution, e.g. Create a Ticket, then we will have a ticketId can correlated to this flow execution. The Callback ID will be passed to the caller and when caller call Aisera flow back, they need to use this Callback ID, like a receipt number. This variable need to share to the caller.
Variable Name
A variable holder to receive additional information from the callback request, e.g. when the caller call Aisera back, they may pass extra information and this variable can be used to represent these extra information. And flow author can use this variable in the following nodes.
User Message
Since the flow execution will be paused here, in conversation use case, we want to show some hint message once flow engine paused the flow execution, so any message put here will be seen by the end user, such as, I am working on your request, will let you know once I am done.
Node Description
As usual, no special function
Each cluster exposed to a public REST API can receive callback. The syntax for the callback is shown below.
Last updated