> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation

> GermainUX Automation turns monitoring and analytics insights into actions, on demand, on a schedule, or automatically.

Availability
2014.1 or later

> [card] [Agentic approach](#agentic-approach-overview)
>
> Observe to validate

> [card] [Outcomes](#business-outcomes)
>
> What it improves

> [card] [Actions](#automated-actions)
>
> Everything it can do

> [card] [Controls](#requirements-and-safeguards)
>
> Safeguards

## Overview

GermainUX Automation turns monitoring and analytics insights into actions.

It can automatically respond to user-experience issues, application errors, business-process failures, performance degradation, infrastructure conditions, or other detected events. Actions can run **on demand, on a schedule, or automatically when defined conditions are met**.

## Agentic approach overview

This enables an **agentic approach to monitoring and operations**, where GermainUX can continuously:

| Phase | Description |
| - | - |
| **Observe** | Monitor users, business processes, applications, and technologies in real time. |
| **Analyze** | Use analytics and AI to identify friction, anomalies, errors, performance issues, impact, and likely causes. |
| **Decide** | Evaluate configured rules, thresholds, context, and conditions to determine what should happen next. |
| **Act** | Notify teams, create or update incidents, call APIs, execute scripts or SQL, run RPA workflows, change operational settings, or perform other authorized actions. |
| **Validate** | Continue monitoring to determine whether the action resolved the issue or whether further action or escalation is required. |

## Example workflow

For example, GermainUX can:

**1. Detect a new application error**

**2. Analyze its impact and context**

**3. Create a ticket with the available evidence**

**4. Notify the responsible team**

**5. Execute an approved remediation**

**6. Validate whether the error stops occurring**

## Other automation capabilities

Automation can also proactively execute synthetic user journeys, validate critical business processes, distribute reports, maintain files, and perform scheduled operational tasks.

## Integration: Monitoring + Analytics + AI + Automation

Together, **Monitoring + Analytics + AI + Automation** allow GermainUX to move beyond identifying issues toward an agentic model that can help **detect, understand, act on, and validate issues continuously**, while keeping actions governed by configured permissions, rules, and organizational controls.

## Business outcomes

Depending on the configured actions, permissions, and integrations, GermainUX Automation can support the following outcomes:

| Area | Business outcomes |
| - | - |
| Application availability and reliability | Reduce downtime by validating critical services and workflows, restarting failed components, executing recovery procedures, and escalating unresolved incidents. |
| Incident response | Reduce notification and response times by automatically alerting the appropriate teams and creating incidents with the available context. |
| User experience | Reduce the duration and impact of user-facing issues by notifying support teams, initiating diagnostics, or executing approved recovery actions. |
| Employee productivity and application adoption | Reduce interruptions and repetitive support work by validating important employee workflows and automating routine corrective actions. |
| eCommerce and conversion | Protect revenue by continuously validating search, login, cart, checkout, payment, and order-confirmation workflows and escalating failures. |
| Business-process continuity | Keep critical workflows operating by identifying failed transactions, initiating recovery procedures, and routing exceptions to the responsible team. |
| Customer experience and support | Accelerate assistance by notifying support teams, creating support records, triggering feedback requests, or initiating approved follow-up workflows when customers encounter significant friction. |
| IT operations | Reduce repetitive work through scheduled scripts, program execution, file maintenance, log-level changes, WebDriver updates, and other authorized tasks. |
| Infrastructure and integrations | Improve service continuity by executing authorized API, SQL, SSH, WMI, script, or program-based actions. |
| Governance and communication | Improve operational consistency through standardized action rules, schedules, notifications, incident creation, and report delivery. |

## Automated actions

### Notifications and incident workflows

| Automated action | What GermainUX can do |
| - | - |
| [Alerts by email or SMS](https://docs.germainux.com/main/alert-email-and-sms.md) | Send templated alerts to configured recipients or distribution lists. |
| [Notifications](https://docs.germainux.com/main/notifications.md) | Deliver operational notifications through configured channels. |
| [ServiceNow](https://docs.germainux.com/main/servicenow.md) | Create or update ServiceNow records through a configured integration. |
| [Slack](https://docs.germainux.com/main/slack.md) | Send messages to configured Slack destinations. |
| [Moogsoft](https://docs.germainux.com/main/moogsoft.md) | Forward events or incidents to Moogsoft. |
| [Watch and Be Notified](https://docs.germainux.com/main/watch.md) | Watch configured data or conditions and notify designated users when matching activity occurs. |

### Application and synthetic actions

| Automated action | What GermainUX can do |
| - | - |
| [Click and Synthetic User Scenarios](https://docs.germainux.com/main/user-click-synthetic-user-scenario.md) | Execute recorded browser workflows for availability checks, transaction validation, and synthetic monitoring. |
| [Program Execution and RPA Bots](https://docs.germainux.com/main/local-program-execution.md) | Run authorized programs and RPA workflows through the GermainUX Engine. |
| [HTTP and HTTPS Execution](https://docs.germainux.com/main/synthetic-http-execution.md) | Call web endpoints, APIs, webhooks, or other HTTP-based services. |
| [Website Crawler](https://docs.germainux.com/main/crawler.md) | Crawl configured websites automatically. |
| [Website Audit and SEO](https://docs.germainux.com/main/website-audit-seo.md) | Execute automated website and SEO audits. |

### System and operational actions

| Automated action | What GermainUX can do |
| - | - |
| [Script Execution](https://docs.germainux.com/main/script.md) | Execute authorized BAT, Perl, PowerShell, Python, or shell scripts. |
| [SSH Execution](https://docs.germainux.com/main/ssh-execution.md) | Run authorized commands on remote systems through SSH. |
| [WMI Execution](https://docs.germainux.com/main/wmi-execution.md) | Execute configured Windows management operations through WMI. |
| [SQL Execution](https://docs.germainux.com/main/sql-execution.md) | Run configured SQL statements or stored procedures against authorized databases. |
| [Log-Level Auto-Setting](https://docs.germainux.com/main/log-level-auto-setting.md) | Change configured application or component log levels automatically. |
| [WebDriver Auto-Update](https://docs.germainux.com/main/browser-auto-update.md) | Maintain compatible browser drivers used by synthetic scenarios. |

### File actions

| Automated action | What GermainUX can do |
| - | - |
| [File Archiving](https://docs.germainux.com/main/file-archiving.md) | Compress and move files according to configured schedules, patterns, and retention rules. |
| [File Deletion and Purge](https://docs.germainux.com/main/automatic-delete-purge-of-files.md) | Remove eligible files according to configured criteria and retention requirements. |
| [File Download](https://docs.germainux.com/main/file-download.md) | Download files from configured sources for subsequent processing. |

### Automated report delivery

| Automated action | What GermainUX can do |
| - | - |
| [Reports](https://docs.germainux.com/main/reporting-automatic.md) | Generate and distribute configured reports automatically on a schedule. |

## Execution controls

Automated actions can be initiated manually, scheduled for recurring execution, or triggered when configured conditions are met.

| Configuration | Purpose |
| - | - |
| [Rules](https://docs.germainux.com/main/rules.md) | Define the conditions and logic that determine when an action runs. |
| [Action Scheduling](https://docs.germainux.com/main/component-scheduling.md) | Run an action at configured times or intervals. |
| [Automated Actions](https://docs.germainux.com/main/automated-actions.md) | Configure notification, remediation, recovery, orchestration, and transactional actions. |

## Requirements and safeguards

Actions run with the permissions, credentials, network access, and GermainUX components configured for the target environment. Availability depends on the selected action and deployment architecture.

> [!WARNING]
>
> Test data-changing, customer-facing, infrastructure, and remediation actions in a non-production environment before enabling unattended execution. Apply least-privilege access and follow the organization’s security, approval, privacy, and change-management policies.

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't find what you need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.