Do we have the option to reuse plugins that we have developed in Agent Studio? We’ve created an approval plugin for one team within our organization, and now another team is requesting a similar solution. Although each team has different data points and systems they connect to, they both want the same approval flow process.
I’m trying to determine if it’s possible to reuse the existing plugin to avoid hitting our plugin limit and to streamline development. If there’s a way to customize or clone the plugin for different data sources while maintaining the core process, that would be ideal.
Could you confirm if this is feasible or suggest the best approach to efficiently handle multiple teams with similar workflow needs? Thanks!
Best answer by Kevin Mok
Hi @hundleymf - You could reuse plugins in Agent Studio. But the underlying logic a plugin is associated with, which is the “body” , whether that is a conversational process or a compound action needs to match each team’s workflow.
A problem I see here, is that you associate a plugin to conversational triggers (a list of utterances). But if all these different teams require different utterances and ways to trigger the plugin, then the plugin will not work correctly, due to having an array of various and incompatible utterances.
So having multiple plugins will most likely be the best path forward here.
If other teams’ workflows are similar but not exactly the same, there’s room to build an abstraction over a compound action that wraps an approval workflow, but that’s a complex topic that should be discussed with the teams. I’d say it makes more sense to build multiple plugins, unless you do see a pattern that could benefit from an abstraction.
Hi @hundleymf - You could reuse plugins in Agent Studio. But the underlying logic a plugin is associated with, which is the “body” , whether that is a conversational process or a compound action needs to match each team’s workflow.
A problem I see here, is that you associate a plugin to conversational triggers (a list of utterances). But if all these different teams require different utterances and ways to trigger the plugin, then the plugin will not work correctly, due to having an array of various and incompatible utterances.
So having multiple plugins will most likely be the best path forward here.
If other teams’ workflows are similar but not exactly the same, there’s room to build an abstraction over a compound action that wraps an approval workflow, but that’s a complex topic that should be discussed with the teams. I’d say it makes more sense to build multiple plugins, unless you do see a pattern that could benefit from an abstraction.
@Kevin Mok Thank you for your help, I really appreciate it! I have a couple more questions. If we get 20 plugins as part of our contract. Does any plugin that is already in Agent Studio Classic that’s been launched count towards that 20? What about any plugin that’s in draft? Or any plugin that launched but it’s only been launched to our developer?
Hey @hundleymf - I don’t have that kind of information when it comes to contract discussions 😅 but I will highly recommend discussing these with your account manager or customer success team!
What I can answer is that draft plugins should not count.
@hundleymf you should also be able to “clone” your work from an existing plugin by “exporting” the plugin and then “importing” it back into your current instance. Then you can tweak it for the other team!
For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.
For current customers who manage their engagement with Moveworks, please login or create your account with the customer button below. For Moveworks Partners, please login or create your account with the partner button below.
