LogoLogo
  • 🖐️Welcome Aboard!
  • 📖Information
    • What is Autom Mate?
    • What is Autom?
    • Features of Autom Mate
    • Architecture of Autom Mate
  • 🤓Learn Autom Basics
  • 📚Libraries
    • Integration
      • Active Directory
      • AFAS
      • Autom Mate
      • Azure Active Directory
      • Azure DevOps
      • BambooHR
      • ChatGPT
      • ConnectWise
      • Database
      • Desktop Actions
      • EasyVista
      • Email
      • Exchange Web Server
      • Exact Online
      • Excel
      • Freshdesk
      • Freshservice
      • Ftp-Sftp
      • GitLab
      • Google Drive
      • Google Workspace
      • HaloITSM
      • Hubspot
      • Intune
      • Ivanti Service Manager
      • Jenkins
      • Jira Confluence
      • Jira Service Management
      • Jira Software
      • Lakeside
      • Lansweeper
      • ME ServiceDesk Plus
      • Microsoft Outlook Calendar
      • Microsoft SharePoint
      • Microsoft Teams
      • My ChatGPT
      • OCR
      • PDF
      • PowerShell
      • Python
      • RESTful Web Service
      • Salesforce
      • ServiceDesk Plus Cloud
      • ServiceNow
      • Slack
      • SolarWinds
      • Stripe
      • TOPdesk
      • Twilio
      • Twitch
      • VMware
      • WhatsApp
      • Word
      • X
      • Xurrent
    • Transform
      • Advanced Actions
      • Array
      • Base64
      • Condition
      • Cryptography
      • CSV
      • Data Table
      • Date
      • File
      • Folder
      • Number
      • Object
      • Repeatable
      • SSH
      • String
      • Text
    • Utility
      • Display Message
      • Grouping
      • Mate DB
      • Mate Drive
      • Time Management
    • Agentic AI (Beta Version)
      • Open AI (Beta Version)
  • 🎇Autom Features
    • Variables
    • Triggers
    • Data Manager
    • Debug
    • Stop Action
    • Function
    • Error Handling and Exception Management
    • Development Mode ( Dev Mode )
    • Business Impact Estimator
  • 🛰️Product Features
    • Dashboard
      • Dashboard
      • Monitoring
      • Alerts
    • Store
      • Autom Store
      • Library Store
    • My Environment
      • Mate Agent
      • Automs
      • Libraries
    • Management
      • User Management
        • Users
        • Roles
        • Forgot Password
      • Vault
      • Webhook & API
      • Alert Management
      • Queue
    • Create Autom
    • Settings
      • Personalization
      • Port & SSL
      • Mail Server
      • License
      • Log Retention
    • Time Zone Management in Autom Mate
  • 💾Installation Setup
    • System Requirements and Ports Configuration
    • Autom Center Installation
      • Autom Center Installation
      • Autom Center Update
    • Mate Agent Installation
      • Mate Agent Installation
      • Mate Agent Update
    • App Installations
      • MS Teams ChatBot Installation
    • Full Chain PFX File Creation Guide
  • 📔Release Notes
    • Amsterdam Edition
      • Amsterdam 3.2.9
      • Amsterdam 3.3.0
    • Boston Edition
      • Boston 4.0.0
      • Boston 4.1.0
      • Boston 4.2.0
      • Boston 4.3.0
        • Boston 4.3.1
        • Boston 4.3.2
        • Boston 4.3.3
        • Boston 4.3.4
        • Boston 4.3.5
        • Boston 4.3.6
        • Boston 4.3.7
      • Boston 4.4.0
        • Boston 4.4.1
      • Boston 4.5.0
  • 🎓Academy
    • 🎓Autom Mate Academy: Basics of Autom Mate
    • 🎓Mastering Automation with Autom Mate: From Workflow Creation
    • 🎓The Ultimate Autom Mate: Teams & Smart Integrations
  • 👔Autom Store & Use Cases
    • 🛒Autom Store Use Cases
    • 🖥️Use Cases
      • How to Create Bidirectional Connection Between JIRA and Xurrent to Open Requests or Tickets
      • Employee Onboarding Process Automation Using Autom Mate
  • ❓FAQ
    • ⚙️General Functionality
    • 🧩Integration Capabilities
    • Data Management and Validation
    • ⁉️Error Handling and Workflow Management
    • Automation Use Cases
    • Connectors and Triggers
    • Custom GPT Models
Powered by GitBook
On this page
  • Autom Center
  • Mate Agent
  • Deployment Types of Autom Mate
  • Cloud Deployment
  • Hybrid Deployment
  • On-premises Deployment
  • How It Works

Was this helpful?

  1. Information

Architecture of Autom Mate

Explains the structural design of Autom Mate, focusing on its components and how they interact to facilitate automation.

PreviousFeatures of Autom MateNextLearn Autom Basics

Last updated 4 months ago

Was this helpful?

Autom Mate's architecture is built on an Automation and Integration platform, designed to automate and streamline business processes effectively. This robust architecture consists of two primary components:

  1. Autom Center

  2. Mate Agent

Autom Center

Autom Center is designed to be user-friendly and accessible to both technical users and citizen developers (non-technical users). It includes the following key modules:

This is a visual tool that allows users to design automation workflows using . Users can create and visualize workflows by arranging (such as sending an , updating a , or calling an ) and connecting them to define the sequence of operations. This approach simplifies the creation of complex automation processes without requiring extensive coding knowledge.

These tools enable users to track the execution of Autom in real-time. Users can view the status of each action, performance metrics, and identify any issues that may arise during execution. modules provide insights into the success or failure of Autom, allowing users to make necessary adjustments for optimization.

This module manages user accounts. It ensures that only authorized users have access to specific functionalities and data within the platform.

A where users can browse, purchase, and download additional automation templates, actions, and modules. This expands the capabilities of Autom Mate by providing ready-made solutions for common automation needs. Users can leverage these templates to quickly implement automation without starting from scratch.

These tools allow administrators to configure settings, manage system operations, and maintain the overall system. This includes tasks such as system monitoring, performance tuning, and security management.


Mate Agent

is a critical component of Autom Mate, operating on the server side. It consists of a microservice infrastructure that includes:


Deployment Types of Autom Mate

Autom Mate provides flexibility in deployment by offering three deployment types: Cloud, Hybrid, and On-Premises. Each type is tailored to meet different infrastructure and operational requirements.

Cloud Deployment

The Cloud Deployment leverages the robust infrastructure of Amazon Web Services (AWS).

  • In this model, both Autom Center and Mate Agent are fully hosted and managed in AWS.

  • This option is ideal for users seeking a fully cloud-based solution that eliminates the need for maintaining local infrastructure.

  • The architecture ensures high availability, scalability, and secure access via AWS services.

Architecture of the Cloud Deployment.

Hybrid Deployment

The Hybrid Deployment combines the benefits of cloud and on-premises environments:

  • Autom Center is hosted on AWS, ensuring centralized management, security, and cloud-based scalability.

  • Mate Agent, however, is installed locally on the user's Local Server or in the user's own cloud environment.

  • This approach is ideal for organizations that require local processing for specific tasks or need to comply with data sovereignty or privacy regulations while benefiting from cloud-based management.

Architecture of the Hybrid Deployment.

On-premises Deployment

The On-Premises Deployment provides the highest level of control for end-users who prefer to manage everything within their own infrastructure:

  • Both Autom Center and Mate Agent are installed on the end-user's Local Server or private cloud environment.

  • To enable logging functionality, the end-user must also install Elasticsearch within their environment.

  • This implementation is best suited for organizations with strict compliance, security, or operational requirements that demand full control over their data and systems.

Architecture of the on-premises deployment.

How It Works

1

User Interaction

  • The Autom information, which includes details about the actions to be performed and the sequence of operations, is sent to the backend operation via a REST API call.

2

Backend Processing

  • The backend handles initial validations, data transformations, and any necessary preliminary steps to set up the Autom for execution.

3

Data Transfer

4

Autom Distribution

  • The microservices handle tasks such as interacting with external systems, processing data, and performing specific automation actions as defined in the Autom.

5

Real-Time Monitoring

  • Real-time monitoring allows users to track the execution of Autom, view logs, and receive alerts for any errors or issues. This ensures that users are always informed about the state of their automation processes and can take corrective actions if needed.

Warnings

  • REST API Call Limit: Be mindful of API rate limits or restrictions, as frequent Autom triggers may impact backend processing speed.

  • Data Format Requirements: Ensure data sent for backend processing meets the required format; incompatible formats can lead to errors or delays.

Hints

  • Real-Time Monitoring: Regularly check the monitoring page to track Autom progress and quickly identify any issues.

  • Automation Distribution: Each library microservice handles specific tasks, so monitoring individual task statuses can help pinpoint performance bottlenecks.

  • Error Management: Set alerts for key Autom's to catch potential errors early and ensure automation runs smoothly.

A user an from the Autom Center's user interface (UI). This can be done through a simple click or based on a predefined schedule or event.

Autom Center's backend operation receives the request and completes the preprocessing phase. This phase involves preparing the data and ensuring it is in the correct format for further processing by the .

The prepared data is transferred to the gateway using gRPC (gRPC Remote Procedure Calls), a high-performance, open-source framework for communication. gRPC ensures efficient and secure data transfer between the backend and the

The gateway distributes Autom actions to the appropriate microservices for execution. Each microservice processes its assigned task and returns the results to the gateway. This communication is also managed using gRPC, ensuring reliability and speed.

Users can the progress of their Autom in real-time from the monitoring page in Autom Center. This feature provides updates and insights into the status and performance of each task within the Autom.

triggers
Autom
Mate Agent
Mate Agent.
library
monitor
📖

Gateway

The gateway acts as the central communication hub, routing data and requests between different microservices. It ensures that each request is directed to the appropriate microservice for processing, facilitating smooth and efficient operations.

Library Microservices

These are specialized services that handle specific automation tasks, such as data processing, system integration, and action execution. Each microservice is developed, deployed, and maintained independently, allowing for easier updates and scalability. The microservices architecture ensures that the system can handle a large number of tasks simultaneously without performance degradation.

Autom:
pre-defined actions
email
database
API
Monitoring Modules:
monitor
Monitoring
User & Role Management:
Market Place (Autom Store):
marketplace
Management Modules:
The Mate Agent
a drag-and-drop interface
Cloud Architecture
Hybrid Architecture
On-premises Architecture
Page cover image