owada | 2020-05-08 04:20:57 UTC | #1
Hello everyone.
I want to use PureCloud Data Action to get a waiting call. I know that you can get queued call by specifying queueId in Input Contract. Is it mandatory to specify the queueId in the Input Contract? I couldn't find a way to get a waiting call by specifying queuename instead of queueId.
What I want to realize this time is to specify the queue name instead of the queueId in the Input Contract and acquire the waiting call.
Please tell me how to achieve this.
Jerome.Saint-Marc | 2020-05-08 07:02:54 UTC | #2
Hello,
Are you talking about the built-in/predefined PureCloud Data Action "Get Estimated Wait Time"? Or a custom one you made? -> If it is the predefined "Get Estimated Wait Time", then no, you must provide the queueId. And in general, you will need to provide the queueId when your perform a request to get an estimated wait time, or if you perform an analytics request (Platform API) to find calls connected to a queue.
Are you doing this request from an Architect flow? If yes, what you can do is to use the "Find Queue" block in your Architect Flow (available via Toolbox - Find - Find Queue). You can provide the Queue Name (as Literal if you know the exact queue name you want) as input, and store the Queue Result in a variable (ex: Flow.MyQueue). If the queue is found, the FindQueue will exit on the Found path. The queueId is then available as Flow.MyQueue.id (that you can use as input in your Data Action).
Regards,
owada | 2020-05-08 11:16:14 UTC | #3
Thank you for your reply.
It is not a pre-defined PureCloud Data Action but a custom one. I'd like to know if I can get queued calls by using queueName with a custom PureCloud Data Action.
Regards,
Jerome.Saint-Marc | 2020-05-08 13:22:07 UTC | #4
Hello,
As you have not said which Platform API request your custom Data Action is using, and where you are invoking this Data Action from, I will reply in general.
So no, these requests use queueId in their filters. Not a queueName.
If you are invoking this Data Action from an Architect flow, you can use the "Find Queue" object before - which will give you the queueId from a queueName. And then invoke your Data Action with the obtained queueId.
Or create a second custom data action, to get queueId from queueName (example: using GET /api/v2/routing/queues). And then invoke your existing data action with the obtained queueId.
system | 2020-06-08 13:29:58 UTC | #5
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: 7744