{ "$result_object_key": [ { "consent_type": "Describes the type of consent", "content_types": "The message types that this subscription supports - can contain 'email' or 'sms_message'", "default_translation": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "id": "The unique identifier representing the subscription type", "state": "The state of the subscription type", "translations": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "type": "The type of the object - subscription" } ]}
v1
Add Contact Subscriptions
Documentation for the Add Contact Subscriptions action for Intercom
{ "$result_object_key": [ { "consent_type": "Describes the type of consent", "content_types": "The message types that this subscription supports - can contain 'email' or 'sms_message'", "default_translation": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "id": "The unique identifier representing the subscription type", "state": "The state of the subscription type", "translations": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "type": "The type of the object - subscription" } ]}
{ "$result_object_key": [ { "consent_type": "Describes the type of consent", "content_types": "The message types that this subscription supports - can contain 'email' or 'sms_message'", "default_translation": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "id": "The unique identifier representing the subscription type", "state": "The state of the subscription type", "translations": { "description": "The description of the subscription type", "locale": "The locale of the subscription type", "name": "The name of the subscription type" }, "type": "The type of the object - subscription" } ]}
You can use the result of the action’s data as inputs to downstream workflow actions.Each fetch action requires an object name, which nests the action’s result data inside the downstream data context in the workflow. See Passing Data Between Actions for how to set it and reference the result from downstream nodes.Here we demonstrate how to refer to this data using the prefix $result_object_key.