{
  "$result_object_key":  {
    "customer_id":  "cus_J2m3K4L5N6O7P8Q9R0S",
    "id":  "card_1NGTaT2eZvKYlo2CZWSctn5n"
  }
}

{
  "$result_object_key":  {
    "customer_id":  "Unique identifier for the customer",
    "id":  "Unique identifier for the payment source"
  }
}

​
Parameters

​
Action
Parameters
​
Customer ID
string

ID This field maps to the destination API customer field.

​
Source
string
required

ID PII This field maps to the destination API source field.

{
  "$result_object_key":  {
    "customer_id":  "cus_J2m3K4L5N6O7P8Q9R0S",
    "id":  "card_1NGTaT2eZvKYlo2CZWSctn5n"
  }
}

{
  "$result_object_key":  {
    "customer_id":  "Unique identifier for the customer",
    "id":  "Unique identifier for the payment source"
  }
}

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

​
PaymentSource
Fetch Action Response Object
​
id
string
required

Unique identifier for the payment source

CEL
$result_object_key.id
Example
"card_1NGTaT2eZvKYlo2CZWSctn5n"
​
customer_id
string

Unique identifier for the customer

CEL
$result_object_key.customer_id
Example
"cus_J2m3K4L5N6O7P8Q9R0S"