{
  "$result_object_key":  {
    "response_body":  null,
    "response_headers":  {
      "key":  null,
      "value":  null
    },
    "status_code":  null
  }
}
{
  "$result_object_key":  {
    "response_body":  null,
    "response_headers":  {
      "key":  null,
      "value":  null
    },
    "status_code":  null
  }
}

Parameters

Action
Parameters
URL
URL
required

This field maps to the destination API url field.

Body
Map<string,dynamic (any)>

HI ID PII This field maps to the destination API body field.

Headers
Map<string,string>
required

This field maps to the destination API headers field.

{
  "$result_object_key":  {
    "response_body":  null,
    "response_headers":  {
      "key":  null,
      "value":  null
    },
    "status_code":  null
  }
}
{
  "$result_object_key":  {
    "response_body":  null,
    "response_headers":  {
      "key":  null,
      "value":  null
    },
    "status_code":  null
  }
}

Result Object Field Details

You can use the result of the action’s data as inputs to downstream workflow actions.

Each fetch action requires a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow.

Here we demonstrate how to refer to this data using the prefix $result_object_key.

HttpPostResult
Fetch Action Response Object
response_body
object
required

Description coming soon

CEL
$result_object_key.response_body
Example
null
response_headers
Map<string,string>
required

Description coming soon

CEL
$result_object_key.response_headers
Example
{
"key":  null,
"value":  null
}
status_code
int64
required

Description coming soon

CEL
$result_object_key.status_code
Example
null