Build better products with our product team.
Objective: To enhance the ease of testing and debugging by providing a feature that allows users to export their automation scripts to CURL commands. This feature aims to facilitate easy testing in Postman and other environments, enabling users to backup their work and re-test their code outside the Moveworks platform to eliminate development environment issues.Key Features: Export to CURL Button: Add a button labelled "Export to CURL" within the Agentic Automation Engine/Creator Studio interface. The button should be easily accessible and prominently placed for quick use. Generate CURL Command: Automatically generate a CURL command based on the current automation script or workflow. Include all necessary headers, parameters, and payloads in the generated CURL command to ensure it replicates the exact request. Copy to Clipboard: Provide an option to copy the generated CURL command to the clipboard with a single click. Ensure the command is formatted correctly for easy pasting into Postman or other tools. Download as File: Offer an option to download the generated CURL command as a text file for easy backup and sharing. Include metadata such as the script name and timestamp in the file for better organization. Integration with Postman: Provide guidance or a direct import option to easily import the CURL command into Postman. Ensure compatibility with Postman's import functionality to streamline the testing process. Benefits:Ease of Testing: Allows users to quickly export their automation scripts to CURL commands for easy testing in Postman and other environments. Backup and Sharing: Facilitates easy backup and sharing of automation scripts by providing downloadable CURL commands. Eliminate Environment Issues: Enables users to re-test their code in different environments, helping to identify and eliminate development environment issues. Improved Debugging: Provides a straightforward way to replicate and debug requests outside the Moveworks platform, enhancing the overall development workflow.
Key DatesPreview: March 2025What is it You can now delay the execution of actions! For developers building with APIs that have asynchronous behavior (e.g. a “start job” endpoint and a “get job results” endpoint), you’ll be able to “sleep” the action for a period of time. FeaturesDelayed Execution - Delay the execution of your action Multiple Units of Time - Support for milliseconds, seconds, minutes, hours, & days Dynamic Sleep Periods - You can vary the sleep period based on your compound action’s data. (e.g. if your “start job” endpoint returns an estimated processing time, you can sleep for that duration). Learn more in our documentation! Check out this “Reminder Plugin” below.Compound Actionaction: output_key: send_plaintext_chat_notification_result action_name: mw.send_plaintext_chat_notification delay_config: seconds: data.delay_in_seconds input_args: message: data.message user_record_id: data.recipient.record_idInput Args Chat Experience
Objective: Enhance the efficiency of the support team and developers by providing a feature that allows the export and download of JSON logs directly from the Creator Studio/Agentic Automation Engine log section.Key Features:Export/Download Functionality: Enable users to export and download JSON logs with a single click, with options to download logs for specific time frames, actions, or events. User-Friendly Interface: Integrate the export/download option seamlessly into the existing user interface. Customizable Log Filters: Allow users to apply filters to the logs before exporting, such as by date, action type, or error codes. Security and Access Control: Implement robust security measures to ensure only authorized users can export and download logs. Integration with Support Tools: Enable integration with existing support tools and platforms for seamless log sharing and collaboration.Benefits:Increased Efficiency: Speeds up the log review process for the support team. Reduced Manual Effort: Eliminates the need for developers to manually copy and paste logs. Improved Collaboration: Facilitates better collaboration between support and development teams. Enhanced User Experience: Provides a user-friendly and secure way to access and manage JSON logs.This feature will significantly enhance the efficiency and effectiveness of both support and development teams, contributing to faster issue resolution and improved user experience.
Objective: To enhance the efficiency of developers by providing a feature that allows them to expand and minimize all sections of JSON logs with a single click. This feature aims to save time and streamline the log review process, reducing the need to manually click through each segment.Key Features: Expand/Minimize All Button: Add a button labeled "Expand All" and "Minimize All" to the JSON log viewer interface. The button should be prominently placed for easy access. Single-Click Functionality: Enable users to expand or minimize all sections of the JSON log with a single click. Ensure the button toggles between expanding and minimizing all sections based on the current state. User-Friendly Interface: Integrate the button seamlessly into the existing user interface of the JSON log viewer. Provide visual feedback to indicate the current state (expanded or minimized) of the log sections. Performance Optimization: Ensure the expand/minimize functionality is optimized for performance, allowing quick and smooth transitions between states. Test the feature with large JSON logs to ensure it performs efficiently without lag. Benefits:Increased Speed: Allows developers to quickly expand or minimize all sections of the JSON log, saving time during the log review process. Improved Efficiency: Reduces the need for manual clicking through each segment, streamlining the workflow and allowing developers to focus on more critical tasks. Enhanced User Experience: Provides a user-friendly and intuitive way to navigate JSON logs, improving overall satisfaction and productivity.
Our Change and Adoption team create a lot of video content for users to answer how-to questions and provide useful information. A really helpful feature would be for our Bot to link to certain points in a video depending on their question.For example, if someone asks how to delete a SharePoint page, the bot will give them a link straight to that point in the video - it would be even better if the part of the video played within the bot in Team!
Hello,Our company uses “Division” and “Service Areas” to define which team a user is in. Division being the parent to the Service Area. We have mapped Moveworks “Department” to our “Service Area” field, but learned that Moveworks does not support lookup by the “Division” field. Please add the ability to look up user’s by Division. This is such a common question that users ask the bot and for it to not be able to do this is quite disappointing.
Consider sorting past batches in reverse order. We have been using a recurring campaign for Onboarding for several months and have to tab through 40+ pages to see this week’s batch.
We love the employee communications tool.Suggestion - Add a type field for sorting, so you can easily pull up templated coms, recurring campaigns etc. I know we can do the same with naming conventions but a field makes it easy.
We have numerous SharePoint articles that cover FAQ’s for a specific area. The articles contain a list of questions within a text web part with the questions formatted as Heading 2 in order to create snippets for each question. When the bot provides the answer, the hyperlink takes the user to the top of the SharePoint article. It would be helpful if the hyperlink could direct the user to that specific heading within the article instead.
Hi, we would like to have the ability to host FAQs outside of the Google Sheet experience.We largely leverage Microsoft, so out preference would be to host a Spreadsheet on OneDrive or SharePoint that could be read by Moveworks, allowing us to control access to the FAQ vs. Moveworks.
I created a post in the wrong place:API with NTLM auth? | CommunityBut it would be very useful to me if NTLM auth was an auth type supported in Creator Studio Actions.
Enhance the bot’s capability to suggest relevant answers based on SharePoint site data. For example, when a user asks, "Who is the point of contact for a new cloud demand in the Americas region?", the bot should retrieve the information directly from the SharePoint site instead of requiring users to manually search for into (source link).The SharePoint site contains contact person names (POCs) for specific service regions. The bot should identify and provide this information to users when they ask about relevant contacts. Reduce manual effort by eliminating the need for users to check the source repeatedly.
We recently implemented the Bot Channel Resolver on Slack.Current workflow:An employee asks a question in the channel. The Bot will send a private DM to the employee with a response. At this point an emoji will appear below the original employee’s query in the channel. Employee receives Bot DM and is asked to rate the response as ‘helpful’ or ‘unhelpful’Our proposed scenario is as follows:We would like the Bot to reply on the same thread instead of sending a private DM, and probably tag a person if it doesn't find the response.Can you advise if the scenario can be implemented on the channel?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.