{
  "$result_object_key":  {
    "status_code":  "202"
  }
}

{
  "$result_object_key":  {
    "status_code":  "Send data event response code"
  }
}

​
Parameters

​
Action
Parameters
​
Event Name
string
required

This field maps to the destination API event_name field.

​
User ID
string

ID This field maps to the destination API user_id field.

​
ID
string

This field maps to the destination API id field.

​
Email Address
string

PII This field maps to the destination API email field.

​
Created At
timing.v1.Timestamp

This field maps to the destination API created_at field.

​
Metadata
Map<string,dynamic (any)>
required

This field maps to the destination API metadata field.

{
  "$result_object_key":  {
    "status_code":  "202"
  }
}

{
  "$result_object_key":  {
    "status_code":  "Send data event response code"
  }
}

​
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.

​
SendEventResponse
Fetch Action Response Object
​
status_code
int64
required

Send data event response code

CEL
$result_object_key.status_code
Example
"202"