- Newest
- Most votes
- Most comments
Thank you for reaching out to us regarding the above query.
From the information shared by you, it seems that you might be using UpdateContactAttributes API for creating user-defined contact attributes associated with the specified contact. Kindly confirm the same.
Now, based on the type of Attributes, you would have to modify the way you would be accessing the attributes in the contact flow. Please refer to the documentation here for more information on the same.
That being said, $.External.AttName is used for Lambda attributes which are returned as key-value pairs from the most recent invocation of an Invoke AWS Lambda function block. Documentation Reference
Therefore, I believe you might be setting user-defined attributes using the API, hence could you try accessing the same using : $.Attributes.name_of_your_destination_key.
I hope that the above information is helpful to you. Having said that, in case you are still facing challenges, please feel free to open a support case with AWS using the following link which would allow us to check the resources internally.
Thank you! I was split 50/50 on if it were $.External or $.Attributes but my issue is the API requires the contact ID. At the time the web engineer is trying to create the attributes, the Connect flow hasn't executed, so there is no ContactID. And even if there was, I'm not sure how the web engineer would retrieve that ContactID from Connect.
Relevant content
- asked 4 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
