Currently, developers don’t have access to which interaction surface a request came from when Moveworks executes an action and sends the payload to the API. It would be great if we could customize the payload of an action to be able to send to the API where the interaction came from, example: ‘zoom’, ‘slack’, ‘movewebchat’, etc. Our use case is that we want to synchronize sending images across all interaction surfaces for a particular agent so if we had access to interaction surface, we could tell if it came to zoom send to the image to the user’s Moveworks chat in zoom, if it came from slack send the image to the user’s Moveworks chat in slack, etc.
4. Future Consideration
Interaction surface being accessible in Agent Studio platforms.
+2Hey
How notification routing works
When Moveworks sends a user notification, it delivers it to the last interaction surface the user talked to the assistant from. So if a user was chatting with the assistant in Slack, the notification goes to Slack. If their last interaction was in Zoom, it goes to Zoom. You don't need to explicitly pass the surface — Moveworks handles that routing automatically.
How to set this up for your use case
The pattern you want is: user triggers a plugin → your external system processes something in the background → sends the result (in your case, an image) back to the user via notification.
Here's the architecture:
The flow:
1. User triggers a plugin through the bot (from whatever surface they're on, Slack, Zoom, Teams, etc.)
2. The plugin makes an API request to your external system
3. Your external system kicks off a background process (generates the image, does whatever processing it needs)
4. When ready, it makes a webhook callback to an Ambient Agent Plugin in Agent Studio
5. The Ambient Agent Plugin invokes a Compound Action with a Notify Expression that contains the image url (more information on sending media through notify HERE)
6. The image is sent back to the user — automatically routed to whatever surface they last interacted with
There isn't a way today to explicitly control which surface the notification goes to, but honestly this ends up being better UX anyway — the notification lands wherever the user currently is, rather than requiring you to manage that routing yourself.
+2Updated idea status 1. New → 4. Future Consideration
Hi
Thanks for the info, I wasn’t aware we could now send images via Notify function now; this will open up a lot more possible use cases we have. One thing I noticed when testing sending an image is that the functionality works as expected in Zoom and Embedded Assistant, but did not fully render the image in Moveworks Web:
Is this an issue with our individual instance or something that isn’t supported yet for the web platform?
Thanks, Ryan
+2Hey
Sign up
Already have an account? Login
If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.
LOGIN WITH MYMOVEWORKS SSO PARTNERS WITH SSO LOGINor
Login or create an account
If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.
LOGIN WITH MYMOVEWORKS SSO PARTNERS WITH SSO LOGINor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.