Hi, @Bruno Mascitti
I don't think there is a single native report that shows "script usage" directly, but you can identify where scripts are being used by checking how they are assigned.
If the script is queue-bound, you can use the Queue API to check which script is configured on each queue:
GET /api/v2/routing/queues/{queueId}
From the queue response, you can validate the script IDs configured for that queue, such as default scripts. This is useful if your agents receive the script based on the queue configuration.
If the script is being opened from an Architect flow, then I would use Architect dependency tools. You can check the flow dependencies or use Dependency Search to see which flows are referencing a specific script/resource.
So my approach would be:
-
Export/list all scripts.
-
Check queues through the Routing Queue API and map script IDs to queues.
-
Check Architect flow dependencies for scripts used in flows.
-
Review outbound campaigns as well, if you use scripts there.
This will not be a "runtime usage report," but it should help you identify which scripts are currently referenced in production and which ones may be legacy candidates for cleanup.
I've done it recently here, and take a long time to validate.
------------------------------
Arthur Pereira Reinoldes
------------------------------