{
  "$result_object_key":  {
    "customer_id":  "123456",
    "stripe_customer_id":  "cus_12345"
  }
}

{
  "$result_object_key":  {
    "customer_id":  "The unique identifier of the customer detail object",
    "stripe_customer_id":  "The ID of the client (in Stripe)"
  }
}

​
Parameters

​
Action
Parameters
​
Stripe Customer Detail Array Index
int64

This field maps to the destination API -1..n stripe_customer_detail array index (defaults to 0), -1 will create a new card field.

​
Stripe Token
string
required

This field maps to the destination API token field.

​
Is Default
bool

This field maps to the destination API is_default field.

{
  "$result_object_key":  {
    "customer_id":  "123456",
    "stripe_customer_id":  "cus_12345"
  }
}

{
  "$result_object_key":  {
    "customer_id":  "The unique identifier of the customer detail object",
    "stripe_customer_id":  "The ID of the client (in Stripe)"
  }
}

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

​
StripeCustomerDetail
Fetch Action Response Object
​
customer_id
string
required

The unique identifier of the customer detail object

CEL
$result_object_key.customer_id
Example
"123456"
​
stripe_customer_id
string
required

The ID of the client (in Stripe)

CEL
$result_object_key.stripe_customer_id
Example
"cus_12345"