Skip to main content
New Participant
July 24, 2026
Solved

Querying employee roster attributes in agent studio?

  • July 24, 2026
  • 1 reply
  • 42 views

Is there a way within agent studio on a scheduled basis to scan across enabled users to see if they meet certain criteria? ie, every day at 9am scan for employees that have been here 4 weeks, and have department = XYZ and role = ABC and function (custom attribute) = DEF. 

Employee comms seems to have some of this functionality, but we want to customize it more and figured agent studio is the best way to go, but im unable to determine if I can query employees via Moveworks or if I have to add a connector to our HRIS/IDP and query those connections instead?

Thanks!

  • Josh
    Best answer by rgeroulo

    Hi ​@jgilmour!

    It is very common to set up Scheduled Jobs to send comms to users via Agent Studio!

    I would recommend reviewing this Scheduled Triggers documentation to review how to set up a cron job to run every day at 9am for example. 

    This Scheduled Trigger is then connected to a Compound Action. This Compound Action will contain your HTTP Action to query for your desired users. Your instance most likely already has a ServiceNow, Azure, Okta, etc. connector that you can use to query. You will not be querying Moveworks directly, but the systems that Moveworks connects to as those are the source of truth. You can add your filtering directly to this HTTP Action using the parameters required for the system.

    Is there a specific IDP that you would like to use that Moveworks is already connected to?

    Let me know if that helps!

    Best

    Ryan

    1 reply

    rgeroulo
    rgerouloAnswer
    Community Manager
    July 27, 2026

    Hi ​@jgilmour!

    It is very common to set up Scheduled Jobs to send comms to users via Agent Studio!

    I would recommend reviewing this Scheduled Triggers documentation to review how to set up a cron job to run every day at 9am for example. 

    This Scheduled Trigger is then connected to a Compound Action. This Compound Action will contain your HTTP Action to query for your desired users. Your instance most likely already has a ServiceNow, Azure, Okta, etc. connector that you can use to query. You will not be querying Moveworks directly, but the systems that Moveworks connects to as those are the source of truth. You can add your filtering directly to this HTTP Action using the parameters required for the system.

    Is there a specific IDP that you would like to use that Moveworks is already connected to?

    Let me know if that helps!

    Best

    Ryan