inter.marcotulio | 2021-10-18 20:45:55 UTC | #1
Hello there.
I`m working on integrating ower 3rd party message system with genesys throuth open messaging api and webhooks.
I did managed to send inbound messages, send agentless messages, eventualy transfer to queue on architect flow, it`s working fine.
But now I need that my 3rds party system updates participant data and this particpant data be available in architect flow, so I can decide wich queue to transfer.
I try sending the participant data along with the messages in the request POST /api/v2/conversations/messages/inbound/open in the field metadata (Map<string, string>) (Additional metadata about this message. )
But I was not able to access this metadata in architect flow get participant data.
I managed to get this information available in architect flow :: get participant data when I send it throuth the following api request: PATCH /api/rest/v2/conversations/{interactionId}/participant{id}/attributes.
But to do so I need the interactionID, that I manually searched in the interactions page on genesys UI. And from the perspective of my 3rds party plataform I did not found a way to retrieve the interactionId.
the send inbound messages API used by the 3rd party plataform returns only the id of the message sent, And I did not found a way to retrieve the interactionId from it.
I realy need to access metadata values in the architect flow generated by my 3rd party message plataform.
I appreciate any help.
refs:
https://developer.genesys.cloud/api/digital/openmessaging
https://developer.genesys.cloud/api/rest/v2/conversations/#post-api-v2-conversations-messages-inbound-open
( and #patch-api-v2-conversations-messages--conversationId--participants--participantId--attributes )
anon39326996 | 2021-10-19 16:34:08 UTC | #2
These features are not yet supported for open messaging but we are working on them and they will be available within the next few weeks. They are noted as something we are working on on our roadmap.
anon39326996 | 2021-11-09 13:27:00 UTC | #3
We will be releasing new enhancements to open messaging this Wednesday. You can see the upcoming features on the coming soon page in resource center: https://help.mypurecloud.com/features-coming-soon/
Open messaging API enhancements
Developers can now take advantage of a variety of open messaging API enhancements, such as inbound and outbound delivery receipts and user-scoped authorization for inbound messaging. Developers can now also pass custom attributes when starting a new conversation or sending a reply, and retrieve a conversation ID using a message ID. This feature requires one of the following subscriptions: Genesys Cloud User 3, Genesys Cloud User 1 Digital Upgrade II, or Genesys Cloud User 2 Digital Upgrade I.
inter.marcotulio | 2021-11-19 19:30:52 UTC | #4
After this last release that made available API that returns conversationId by messageId, I managed to send participant data to the interaction using the conversationId and it works.
But doing this way the participant data is available only from the second message. Sometimes I need to transfer the client to a queue in the very first message.
is there by any chance to make available to architect flow the the metadata field sent in POST inbound messages?
anon39326996 | 2021-11-22 13:32:01 UTC | #5
Hello there! It sounds like you may be setting the metadata field. Can you try setting the message.channel.metadata.customAttributes field?
anon39326996 | 2021-11-19 22:23:55 UTC | #6
In case you are using our SDKs, found an issue where the new customAttributes field doesn't show up in the SDKs yet. We'll be fixing that.
If using the API directly, the documentation covers how to send in the custom attributes: https://developer.genesys.cloud/api/digital/openmessaging/inboundMessages#inbound-text-message-with-custom-attributes-in-channel-metadata
inter.marcotulio | 2021-11-22 13:30:23 UTC | #7
Hello Lucie. Thanks for the answer.
I had miss this message.channel.metadata.customAttributes field, it is exacly what I was looking for.
my problem is solved. Thank you!!
ps. I missed it because this documentation is outdated: https://developer.genesys.cloud/api/rest/v2/conversations/#post-api-v2-conversations-messages-inbound-open
I was trying to send it on message.metadata
system | 2021-12-22 13:14:58 UTC | #8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 12396