Legacy Dev Forum Posts

Jeremy_MONZO | 2023-10-18 14:54:06 UTC | #1

Hello, I have 4 Messenger Configurations differents for the webmessaging. All have the same configuration except the target queue which is different for each configuration. I looking a way to build the same Inbound message startegy in Architect (instead create 4 different strategies) with diffrent target queue. Is there a simple way in architect to retrieve the Messenger configuration in order to configure the target queue or something which can differentiate the configurations used for the message?

thanks jeremy

zubair | 2023-10-18 18:37:39 UTC | #2

Hi, Other than different destination queues, what's the reason of using 4 different Messenger Configurations. i.e. do you have 4 different websites/web pages?

Jeremy_MONZO | 2023-10-18 18:58:06 UTC | #3

Hi Zubair,

yes it is 4 differents messenger configuration with a different visual and located on different web pages. thanks for hints

zubair | 2023-10-18 19:30:29 UTC | #4

Hi Jeremy,

Right so two ways I can think of:

1. You can use the Database.set command to write Custom Attribute to the interaction. In your case it could be the Unique Name for each webpage source.

Then build a Data Action using GET /api/v2/conversations/{conversationId} to retrieve those attributes within Architect Flow and make Routing decision based on the Attribute values.

2. Build a Data Action using *GET /api/v2/conversations/{conversationId}* to retrieve the Deployment Name which can be found under *participants[0].messages[0].toAddress.name* OR *participants[1].name* in the response. Then call that data action in the Architect Flow and make Routing decision based on the values

In both cases, for the data action input, you can use the built in variable *Message.ConversationID* to supply the conversation id

cheers

Angelo_Cicchitto | 2023-10-19 10:27:17 UTC | #5

@Jeremy_MONZO a more simple approach would be to pass your "queue" identifier (really, this can be any label) using Custom Attributes (Database.set), and then simply retrieve it via Get Participant Data action in Architect Flow. Any Custom Attribute will be mapped to Participant Data using the same name value.

Jeremy_MONZO | 2023-10-20 13:44:23 UTC | #6

Hi Guys, thanks all for your replies.

I have finally used the Data Action using *GET /api/v2/conversations/{conversationId}* for retrieve the deployment key which can be found found in *participants[0].messages[0].toAddress.addressNormalized*

system | 2023-11-20 13:44:19 UTC | #7

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

This post was migrated from the old Developer Forum.

ref: 22617