{ "$result_object_key": [ { "card_type": "The brand of the card", "card_type_label": "The type of card indicated by the user. Defaults to personal, Options are 'hsa', 'fsa', and 'personal'", "expiration": "The expiration date of the card", "id": "The unique identifier of the customer detail object", "last_four": "The last 4 digits of the credit card", "stripe_id": "The ID of the client (in Stripe)" } ]}
v1
Get Stripe Customer Details
Documentation for the Get Stripe Customer Details action for Healthie
{ "$result_object_key": [ { "card_type": "The brand of the card", "card_type_label": "The type of card indicated by the user. Defaults to personal, Options are 'hsa', 'fsa', and 'personal'", "expiration": "The expiration date of the card", "id": "The unique identifier of the customer detail object", "last_four": "The last 4 digits of the credit card", "stripe_id": "The ID of the client (in Stripe)" } ]}
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.