Skip to main content
New Participant
September 3, 2026
3. Existing Functionality/Native Skill

Subject: Feature Request: Proactive Health Monitoring & Credential Alerting Dashboard

Related products:Agent StudioEmployee Experience InsightsAnalytics
  • September 3, 2026
  • 2 replies
  • 27 views

Description: Dear Team,

I would like to understand whether Moveworks currently provides any native capabilities within the Control Center, or via API, for the following monitoring and alerting requirements. Additionally, if any of these capabilities are already available, please let us know whether they are currently being utilized by any customer.

1. Outage Monitoring and Visibility
Outage Notifications: Immediate alerts when the bot, or any of its critical connected integrations, experiences downtime.
Root Cause Visibility: Detailed logs indicating what failed, when the outage started, and which specific service, system, or connector was impacted.
Historical Uptime Tracking: Access to historical uptime data and incident logs for reporting and audit purposes.

2. Integration Credential Expiration Alerts
ServiceNow: Proactive notifications (for example, 30/15/7 days in advance) for expiring service account passwords or API tokens.
Microsoft Graph: Expiration monitoring for Azure AD / Entra ID client secrets and tokens used by the bot.

3. Certificate and Key Lifecycle Management
AWS Certificates: Monitoring and alerting for AWS infrastructure certificates, specifically in the Corning environment.
JWT and JWKS Keys: Alerts for upcoming expiration of JSON Web Tokens (JWTs) or keys used for custom API authentication and SSO.

4. Alerting and Notification Channels
The ability to route these notifications through preferred enterprise channels, such as:

Automatic ITSM incident creation
Email notifications to the admin team
Webhook-based alerts to Slack or Microsoft Teams
Request for Clarification
Could you please confirm:

Whether any of the above capabilities are currently available natively within Moveworks Control Center;
Whether they can be accessed, configured, or exposed via API;
Whether any customers are currently using these capabilities; and
If not currently available, whether this can be considered a formal feature enhancement request for the product team.
Thank you for your support. I look forward to your guidance.

2 replies

Kevin Mok
Community Manager
September 9, 2026

Hey ​@mandarmarkandeya - these aren’t native plugins that we have but they are something you can build using Agent Studio. It would be mostly through Ambient Agents, I am sure these platforms you mentioned can trigger webhooks and hit a listener or you can use scheduled flows to hit these systems’ APIs and check for changes and then process the data as mentioned above.

Kevin Mok
Community Manager
September 9, 2026
Updated idea status1. New3. Existing Functionality/Native Skill