# 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.