> For the complete documentation index, see [llms.txt](https://docs.inopli.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inopli.com/rpa-soar/overview.md).

# Overview

The <mark style="color:green;">RPA module</mark> in Inopli provides a centralized and visual environment for orchestrating automated actions in response to security events, repetitive tasks, and operational workflows. Built with flexibility and scalability in mind, it empowers <mark style="color:green;">SOC teams</mark> to define playbooks using a no-code editor, reducing response time and human intervention.

This section introduces the core components of the RPA module, organized into distinct functional areas that work together to enable automation at every level of security operations:

***

* <mark style="color:green;">**Automations**</mark>\
  Full workflow definitions executed based on triggers such as timers, detection rules, or analyst actions. Each automation can contain branching logic, error handling, and multi-step processing. There is no limit to the number of playbooks that can be created, allowing the SOC team to automate both recurring processes and complex incident responses without restriction.
* <mark style="color:green;">**Components**</mark>\
  Reusable building blocks used inside automations. These are modular actions or sequences that can be shared across different workflows to ensure consistency and reduce duplication.
* <mark style="color:green;">**Integrations**</mark>\
  This area manages all third-party connections used by the playbooks. Inopli RPA supports a growing library of connectors, with dozens of native integrations available out-of-the-box. Whether connecting to SIEM platforms, messaging tools, ticketing systems, or cloud providers, each integration is configurable and can be used in multiple automation flows simultaneously.
* <mark style="color:green;">**Appliances**</mark>\
  Remote execution units for running automations in isolated or controlled environments. These are typically used when actions must occur in segmented networks or require direct access to internal infrastructure.
* <mark style="color:green;">**Tasks**</mark>\
  A kanban-style monitoring interface showing the current state of every automation task, grouped into categories such as inactive, pending, running, failed, and successful. This area gives visibility into execution flow and allows analysts to audit task lifecycles and outcomes.
* <mark style="color:green;">**Dashboard**</mark>\
  A visual hub summarizing the overall status of the automation framework. It includes real-time insights into automation coverage, task success rates, component health, and new custom logic or knowledge deployed by the team.

<mark style="color:green;">Inopli RPA</mark> is built to support enterprise-scale automation, allowing SOCs to create and manage hundreds or thousands of workflows without architectural limitations. The modular design, deep integration capabilities, and visual flow editor make it possible to rapidly deploy new automations and adjust existing ones as threats and operational demands evolve.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inopli.com/rpa-soar/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.