{
  "$result_object_key":  {
    "delivery_id":  "123452",
    "message":  "Queued. Thank you."
  }
}

{
  "$result_object_key":  {
    "delivery_id":  "Unique ID for the message",
    "message":  "The message returned by the mailing server"
  }
}

​
Parameters

​
Action
Parameters
​
Domain
string (Domain)
required
​
From
string
required
​
Reply To
string
​
BCC
[]string
required

PII

​
Subject
string
required
​
Body
required
​
Subscription Topic
string (Subscription Topic)
required
{
  "$result_object_key":  {
    "delivery_id":  "123452",
    "message":  "Queued. Thank you."
  }
}

{
  "$result_object_key":  {
    "delivery_id":  "Unique ID for the message",
    "message":  "The message returned by the mailing server"
  }
}

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

​
SendEmailResult
Fetch Action Response Object
​
delivery_id
string
required

Unique ID for the message

CEL
$result_object_key.delivery_id
Example
"123452"
​
message
string
required

The message returned by the mailing server

CEL
$result_object_key.message
Example
"Queued. Thank you."