# Lists

The <mark style="color:green;">**Lists**</mark> <mark style="color:green;"></mark><mark style="color:green;">feature</mark> in the <mark style="color:green;">Inopli RPA</mark> module enables the creation of structured collections of knowledge and information that can be dynamically referenced or modified during automation or task executions. These lists act as centralized data sources such as user inventories, blocked IPs, or validated entities used to inform decisions, enhance processing logic, and enable conditional flows.

***

### **Purpose and Design**

* <mark style="color:green;">**Dynamic Data Sources**</mark>\
  Each list can store rows of values organized in fields (columns), with configurable data types such as strings, numbers, booleans, or sensitive fields (masked). These lists provide external data context to workflows at runtime.
* <mark style="color:green;">**Automation-Editable**</mark>\
  Lists can be both read from and written to by automations and tasks. This enables automations to evolve based on previous execution outcomes, such as updating a list of flagged users or appending newly discovered IOCs.
* <mark style="color:green;">**Structured and Searchable**</mark>\
  List entries are paginated and searchable, with visibility into each field’s values. Fields can be renamed or deleted, and entries can be added or removed via both UI and automation logic.

***

### **Benefits**

* <mark style="color:green;">**Centralized Knowledge Management**</mark>\
  Lists reduce fragmentation of information by providing a shared source of truth across automations, ensuring consistency in decision-making logic.
* <mark style="color:green;">**Runtime Adaptability**</mark>\
  Automations can modify list contents as they execute, enabling the system to adapt in real-time based on live data and incident context.
* <mark style="color:green;">**Seamless Integration with Workflow Logic**</mark>\
  Lists can be easily bound to input/output nodes in automations and components, streamlining interactions between logic and data without custom development.

***

This capability is essential for use cases requiring evolving context, such as threat intel watchlists, exception tracking, or operational allow/deny lists.

<figure><img src="https://2621223932-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLTQJomzpe5BTzHSLQPAt%2Fuploads%2Fbe32dTJwTvcxyQJRYYPO%2Fimage.png?alt=media&#x26;token=edd66af8-d1b2-4084-bcf8-5d0293fa3b86" alt=""><figcaption></figcaption></figure>
