Action payloads
Conditional connections
In a pipeline, you may set up conditional connections between consecutive actions. With this type of connection, the target nodes will rely on the success or failure of the prior node.
Success cases
Listed below are some examples of the payloads received based on the action types of the initial and target nodes, if the initial node has succeeded.
Custom action success
Target: Webhook node input
The input payload will contain the output of the previous custom action node.
Target: Custom action node input
The input will contain an event payload and a context payload. The event payload will be the original event’s payload, and the context payload will contain the output of the previous custom action node.
Target: Agent node input
Process the following data:
# This section will display the output payload of the previous custom action node.Email success
Target: Webhook node input
The input payload will contain the context payload of the original event node.
Target: Custom action node input
The input will contain an event payload and a context payload. The event payload will be the original event’s payload, and the context payload will contain the context payload of the original event node.
Target: Agent node input
Process the following data:
# This section will display the context payload of the original event node.
Webhook success
Target: Webhook node input
The input payload will contain the output payload of the previous webhook node.
Target: Custom action node input
The input will contain an event payload and a context payload. The event payload will be the original event’s payload, and the context payload will contain the output payload of the previous webhook node.
Target: Agent node input
Process the following data
# This section will display the output payload of the previous webhook node.Agent success
Target: Webhook node input
The input payload will contain the JSON output of the previous agent node.
Target: Custom action node input
The input will contain an event payload and a context payload. The event payload will be the original event’s payload, and the context payload will contain the JSON output of the previous agent node.
Target: Agent node input
Process the following data:
# This section will display the JSON output of the previous agent node.Failed cases
Listed below are some examples of the payloads received based on the action types of the initial and target nodes, if the initial node has failed.
Custom action failure
Target: Webhook node input
{
"prev_node": {
"event": {},
"context": {}
},
"error": {
"exc_type": "error_type",
"exc_value": "error_value"
}
}Target: Custom action node input
{
"prev_node": {
"event": {},
"context": {}
},
"error": {
"exc_type": "error_type",
"exc_value": "error_value"
}
}Target: Agent node input
Process the following data:
{
"prev_node": {
"event": {},
"context": {}
},
"error": {
"exc_type": "error_type",
"exc_value": "error_value"
}
}Email failure
Target: Webhook node input
{
"prev_node": {
"email_body": empty
},
"error": {
}
}Target: Custom action node input
{
"prev_node": {
"email_body": empty
},
"error": {
}
}Target: Agent node input
Process the following data:
{
"prev_node": {
"email_body": empty
},
"error": {
}
}Webhook failure
Target: Webhook node input
{
"prev_node": {
"headers": {},
"body": "always text"
},
"error": {
"status": 400,
"response": "TEXT"
}
}Target: Custom action node input
{
"prev_node": {
"headers": {},
"body": "always text"
},
"error": {
"status": 400,
"response": "TEXT"
}
}Target: Agent node input
Process the following data:
{
"prev_node": {
"headers": {},
"body": "always text"
},
"error": {
"status": 400,
"response": "TEXT"
}
}Agent failure
Target: Webhook node input
{
"prev_node": {
"prompt": "text"
},
"error": {
}
}Target: Custom action node input
{
"prev_node": {
"prompt": "text"
},
"error": {
}
}Target: Agent node input
Process the following data:
{
"prev_node": {
"prompt": "text"
},
"error": {
}
}Updated 3 days ago