> 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/components.md). # Components The **Components** feature of the Inopli RPA module enables the creation of **reusable automation blocks**, encapsulating logic, conditions, and actions into modular units. These components act as micro-playbooks that can be referenced across multiple larger automation workflows, ensuring consistency, efficiency, and simplified maintenance. *** ### Purpose and Design * **Encapsulated Logic**\ Each component is built to perform a specific function such as enriching data, validating inputs, triggering notifications, or interacting with third-party systems. Once created, the component behaves as a **self-contained automation object**, with its own input/output structure and execution context. * **Drag-and-Drop Integration**\ Components are available directly within the **visual automation builder**, where they can be dragged into larger playbooks and reused across various steps and branches without the need to redefine their logic. * **Parametrization and Input Binding**\ Each component can accept **dynamic parameters** at runtime, making them adaptable to different scenarios. Inputs and outputs are clearly defined, enabling clean interfacing with other playbook elements. *** ### Benefits * **Reusability Across Automations**\ By modularizing recurring logic into components, teams reduce duplication and improve scalability. A single update to a component reflects across every automation that uses it, streamlining change management. * **Faster Playbook Assembly**\ Analysts can rapidly assemble new automations using a growing library of existing components, focusing on business logic instead of low-level implementation details. * **Operational Consistency**\ Components enforce **standardization of procedures**, ensuring that critical actions (like asset tagging, email notifications, or escalation triggers) follow approved, centrally managed workflows. --- # 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/components.md?ask= ``` 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.