Skip to main content
6. Delivered

Actions: On-premise Connectors

Related products:Agent Studio
  • October 3, 2024
  • 10 replies
  • 241 views
Ajay Merchia
Forum|alt.badge.img+2

Key Dates

  • Limited Preview: February 2025
  • Preview: July 2025

What is it

  • Connect your Creator Studio plugins to on-premise systems via the Moveworks Agent

Features

What does this feature do?

  • The Moveworks On Prem Agent (not to be confused with AI Agents 😉) allows customers to integrate their on-premise systems to the Moveworks Platform
  • CREST Connectors can now be configured to be used with the MW Agent, enabling CREST use cases to be on prem

How can I access this feature?

  • The setup experience is the exact same as System Connectors that are on prem
  • To configure:
    1. Configure the MW On Prem Agent with a REST Connector + Service Name
    2. Create a new CREST Connector with On Premise Auth  and specify the Service Name from step a
    3. Use the CREST Connector in any CREST use case like you would any other connector

10 replies

Ajay Merchia
Forum|alt.badge.img+2
  • Ajay Merchia
  • Author
  • Community Manager
  • October 3, 2024
1. New→2. On Roadmap
    M
    Forum|alt.badge.img+1

    This would be a huge benefit for us in Gov cloud.

      Derrick
      Forum|alt.badge.img+3
      • Derrick
      • Inspiring
      • February 26, 2025

      Depending on the features, this sounds like it would be a huge help for me as well. I would love to see usage samples for ideas on how it may potentially be used. 

        samujala
        Forum|alt.badge.img+1
        • samujala
        • Employee
        • February 28, 2025
        2. On Roadmap→5. Limited Preview
          A
          Forum|alt.badge.img+4
          • alopez
          • Known Participant
          • February 28, 2025
          2. On Roadmap→5. Limited Preview

          How many I get into the limited preview for this feature?

          Please and thank you!

          -Anthony

          Derrick
          Forum|alt.badge.img+3
          • Derrick
          • Inspiring
          • March 3, 2025

          ​@Ajay Merchia Please pardon my ignorance, do I just need to setup a new instance of the agent then?

          Key Dates

          • Limited Preview: Q1 2025
          • Preview: Q3 2025

          What is it

          • Connect your Creator Studio plugins to on-premise systems via the Moveworks Agent

          Features

          What does this feature do?

          • The Moveworks On Prem Agent (not to be confused with AI Agents 😉) allows customers to integrate their on-premise systems to the Moveworks Platform
          • CREST Connectors can now be configured to be used with the MW Agent, enabling CREST use cases to be on prem

          How can I access this feature?

          • The setup experience is the exact same as System Connectors that are on prem
          • To configure:
            1. Configure the MW On Prem Agent with a REST Connector + Service Name
            2. Create a new CREST Connector with On Premise Auth  and specify the Service Name from step a
            3. Use the CREST Connector in any CREST use case like you would any other connector

           

            neal
            • neal
            • Employee
            • March 4, 2025

            ​@Ajay Merchia Please pardon my ignorance, do I just need to setup a new instance of the agent then?

            Key Dates

            • Limited Preview: Q1 2025
            • Preview: Q3 2025

            What is it

            • Connect your Creator Studio plugins to on-premise systems via the Moveworks Agent

            Features

            What does this feature do?

            • The Moveworks On Prem Agent (not to be confused with AI Agents 😉) allows customers to integrate their on-premise systems to the Moveworks Platform
            • CREST Connectors can now be configured to be used with the MW Agent, enabling CREST use cases to be on prem

            How can I access this feature?

            • The setup experience is the exact same as System Connectors that are on prem
            • To configure:
              1. Configure the MW On Prem Agent with a REST Connector + Service Name
              2. Create a new CREST Connector with On Premise Auth  and specify the Service Name from step a
              3. Use the CREST Connector in any CREST use case like you would any other connector

             

            Hi Derrick, You should not perform a new instance of your agent. All active agents need to have the same configs, since they round robin through requests from a queue. You should update your existing agent with configs for your new REST endpoint. If you do not have an Agent set up yet, you will need to do that by following the instructions here: https://help.moveworks.com/docs/moveworks-agent

            Neal Vasan
            Derrick
            Forum|alt.badge.img+3
            • Derrick
            • Inspiring
            • March 4, 2025

            ​@Ajay Merchia Please pardon my ignorance, do I just need to setup a new instance of the agent then?

            Key Dates

            • Limited Preview: Q1 2025
            • Preview: Q3 2025

            What is it

            • Connect your Creator Studio plugins to on-premise systems via the Moveworks Agent

            Features

            What does this feature do?

            • The Moveworks On Prem Agent (not to be confused with AI Agents 😉) allows customers to integrate their on-premise systems to the Moveworks Platform
            • CREST Connectors can now be configured to be used with the MW Agent, enabling CREST use cases to be on prem

            How can I access this feature?

            • The setup experience is the exact same as System Connectors that are on prem
            • To configure:
              1. Configure the MW On Prem Agent with a REST Connector + Service Name
              2. Create a new CREST Connector with On Premise Auth  and specify the Service Name from step a
              3. Use the CREST Connector in any CREST use case like you would any other connector

             

            Hi Derrick, You should not perform a new instance of your agent. All active agents need to have the same configs, since they round robin through requests from a queue. You should update your existing agent with configs for your new REST endpoint. If you do not have an Agent set up yet, you will need to do that by following the instructions here: https://help.moveworks.com/docs/moveworks-agent

            @Ajay Merchia got it that makes sense, our agent instances for sure don't have rest enabled. 

            Is there a minimum agent version that works?
            Is it possible to get a sample of the config file where this is enabled so I can modify mine to enable it?
             

            samujala
            Forum|alt.badge.img+1
            • samujala
            • Employee
            • March 17, 2025

            ​@Derrick 

            1. We recommend version 2.10.* or higher to ensure that you have the latest changed. See On Premise Auth Connectors Documentation. 
            2. See example configs here, Jira and Confluence are examples of rest_configs. The Agent Installation should guide you through this process as well.

            Let me know if you have any questions!

            Derrick
            Forum|alt.badge.img+3
            • Derrick
            • Inspiring
            • May 27, 2025

            ​@Derrick 

            1. We recommend version 2.10.* or higher to ensure that you have the latest changed. See On Premise Auth Connectors Documentation. 
            2. See example configs here, Jira and Confluence are examples of rest_configs. The Agent Installation should guide you through this process as well.

            Let me know if you have any questions!

            Hi ​@samujala , 
            The first link in your post doesn’t work anymore. Is there a new location for that documentation?

            Terms & ConditionsCookie settingsAccessibility statement