Skip to main content
Sticky

Community Post Guidelines for Agent Studio

  • October 14, 2025
  • 1 reply
  • 70 views
Kevin Mok
Forum|alt.badge.img+1

Purpose

Welcome to the Agent Studio category of our community forum! Agent Studio is a platform that empowers developers to build Agentic Plugins to automate and run business processes using Moveworks’ Agentic Automation Engine. Whether you're ideating new use cases, architecting solutions, or troubleshooting issues, this forum is your space to collaborate with other developers and get support from the Moveworks community. Please follow these guidelines when posting to ensure we can assist you effectively.

 

Required Information for Posts

When creating a post in the Agent Studio category, please include the following details to help us understand your query and provide the best possible assistance:

  1. Type of Help Needed 
    Specify whether you need help with:
    1. Ideating a use case
    2. Architecting a solution
    3. Troubleshooting an issue
    4. Other (please describe)
  2. Plugin Information

    1. Name: The name of the plugin you are working on.

    2. Description: A brief explanation of what the plugin is intended to do (e.g., automate a specific business process).

    3. Functionalities or Actions: There are specific features or actions within the plugin that you need help with.

  3. Research and Logs

    1. Have you checked the logs for errors or relevant information? If so, please share any relevant log excerpt and screenshots.

    2. Describe any research or troubleshooting steps you’ve already taken to resolve the issue.

  4. Connector or Integration
    Specify which business system or API connector your plugin uses (e.g., Salesforce, Jira, ServiceNow). This helps us understand the integration context.

  5. Marketplace Plugin
    If applicable, indicate whether the plugin was installed from the Moveworks AI Agent Marketplace. Provide the plugin’s name and link

  6. Problem Description (for Troubleshooting)

    1. Issue Description: Provide a detailed explanation of your issue.

    2. Steps to Reproduce: List the steps to replicate the problem.

    3. Expected vs. Actual Results: Describe what you expected to happen and what occurred.

    4. Error Messages: Include any error messages or screenshots, if available.

  7. Use Case Description (for Ideation/Architecting)

    1. Business Problem: What problem are you trying to solve with your plugin?

    2. Goals: What are the objectives for your plugin?

    3. Requirements or Constraints: Are there specific requirements or limitations?

    4. Inspirations: Do you have examples or inspirations from similar use cases?

  8. Additional Information
    Include details that might help the community understand your query, such as specific configurations, dependencies, or related issues.

 

Before Posting

  • Search First: Check the forum, Agent Architect, and Moveworks documentation to see if your question has been answered. 

  • Be Clear and Concise: Ensure your post is well-organized and includes all relevant details to avoid back-and-forth.

 

Why These Guidelines?

Providing detailed and specific information helps the community and Moveworks support team respond more effectively. For troubleshooting, details like logs, error messages, and environment specifics allow us to pinpoint issues quickly, reducing support load and enhancing self-service. For ideation or architecting, sharing your goals and constraints helps us provide tailored suggestions.

 

Additional Tips

  • Formatting: Use clear formatting for code, logs, or error messages (e.g., markdown code blocks) to improve readability.

  • Follow Up: If you resolve your issue, consider updating your post to share the solution, helping others in the community.

Following these guidelines will contribute to a vibrant and helpful Agent Studio community. Thank you for being a part of it!

    This topic has been closed for replies.

    1 reply

    Kevin Mok
    Forum|alt.badge.img+1
    • Kevin Mok
    • Author
    • Community Manager
    • October 14, 2025

    Example Posts

    To help you craft effective posts, here are examples of good and bad posts. These examples demonstrate how to provide sufficient context, follow the guidelines, and avoid common mistakes.

     

    Good Post: Troubleshooting a Plugin Issue

    Title: Error in "TaskSync" Plugin with Jira Connector - Need Troubleshooting Help
    Post:
    Hello Agent Studio Community,

    I’m seeking troubleshooting help for an issue with a plugin. Here are the details:

    • Type of Help: Troubleshooting

    • Plugin Information:

      • Name: TaskSync

      • Description: Automates task creation in Jira based on employee requests.

      • Functionalities: Creates Jira tickets and syncs status updates.

    • Connector: Jira Cloud API (v3)

    • Marketplace Plugin: Yes, TaskSync v1.2.3 from the Moveworks AI Agent Marketplace.

    • Problem Description:

      • Issue: The plugin fails to create tickets in Jira, throwing an error: HTTP 403: Forbidden.

      • Steps to Reproduce:

        1. Configure TaskSync with Jira connector.

        2. Submit a task request via Moveworks chat.

        3. Plugin attempts to create a ticket but fails.

      • Expected vs. Actual Results: Expected a ticket to be created in Jira; instead, the error occurs, and no ticket is created.

      • Error Messages: HTTP 403: Forbidden - Invalid API token or permissions.

    • Research and Logs:

      • Checked logs in Agent Studio: 2025-06-10 10:15:23 ERROR: Failed to authenticate with Jira API.

      • Verified API token in Jira; it seems valid but may need specific permissions.

      • I searched Moveworks documentation but couldn’t find the required Jira permissions details.

    • Additional Information: The plugin worked fine last week but started failing after a Jira update. I suspect a permissions issue, but I need help confirming.

    Any suggestions on troubleshooting this error or checking Jira permissions? Thanks!

    Why This Post Is Good:
    This post includes all required details: type of help, organization, plugin specifics, connector, marketplace info, a clear problem description with steps to reproduce, logs, research, and environment details. It’s well-organized, uses markdown for readability, and provides enough context for the community to offer targeted help. The tone is professional, and the post respects community guidelines.

     

    Bad Post: Vague Troubleshooting Request

    Title: Plugin Not Working
    Post:
    Hey, my plugin isn’t working. I’m using it with Salesforce, and it just fails. Can someone help? What’s wrong with it?

    Why This Post Is Bad:
    This post lacks critical details, making it difficult for the community to assist:

    • Missing Information: No organization name, plugin name, or description of its purpose.

    • Vague Problem: “Isn’t working” and “just fails” provide no specifics on the issue, steps to reproduce, or error messages.

    • No Research or Logs: Doesn’t mention checking logs or prior troubleshooting steps.

    • Incomplete Context: Mentions Salesforce but not the connector version or Agent Studio environment.

    • Marketplace Status: Unclear if the plugin is from the marketplace.
      This post likely requires multiple follow-up questions, delaying assistance and frustrating community members.

      Terms & ConditionsCookie settingsAccessibility statement