{
  "$result_object_key":  {
    "created_at":  "2025-01-17T10:57:05Z",
    "id":  "AC123abc"
  }
}

{
  "$result_object_key":  {
    "created_at":  "When the message was created",
    "id":  "ID of the message created"
  }
}

​
Parameters

​
Action
Parameters
​
From
string (Phone Number)
required

ID This field maps to the destination API from field.

​
To
string
required

PII This field maps to the destination API to field.

​
Content
string
required

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

{
  "$result_object_key":  {
    "created_at":  "2025-01-17T10:57:05Z",
    "id":  "AC123abc"
  }
}

{
  "$result_object_key":  {
    "created_at":  "When the message was created",
    "id":  "ID of the message created"
  }
}

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

​
SendTextMessageResponse
Fetch Action Response Object
​
id
string
required

ID of the message created

CEL
$result_object_key.id
Example
"AC123abc"
​
created_at
timing.v1.Timestamp
required

When the message was created

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