{
  "$result_object_key":  {
    "date_created":  "2025-01-17T10:57:05Z",
    "date_sent":  "2025-01-17T10:57:05Z"
  }
}

{
  "$result_object_key":  {
    "date_created":  "When the message resource was created",
    "date_sent":  "When the message was sent"
  }
}

​
Parameters

​
Action
Parameters
​
To
string
required

PII This field maps to the destination API to field.

​
Body
required

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

​
Subscription Topic
string (Subscription Topic)
required
{
  "$result_object_key":  {
    "date_created":  "2025-01-17T10:57:05Z",
    "date_sent":  "2025-01-17T10:57:05Z"
  }
}

{
  "$result_object_key":  {
    "date_created":  "When the message resource was created",
    "date_sent":  "When the message was sent"
  }
}

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

​
MessageSent
Fetch Action Response Object
​
date_created
timing.v1.Timestamp

When the message resource was created

CEL
$result_object_key.date_created
Example
"2025-01-17T10:57:05Z"
​
date_sent
timing.v1.Timestamp

When the message was sent

CEL
$result_object_key.date_sent
Example
"2025-01-17T10:57:05Z"