> For the complete documentation index, see [llms.txt](https://docs.rely.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rely.io/plugins-and-automation/automation-rules/overview-and-use-cases.md). # Overview and Use Cases Automation Rules in Rely.io enhance the efficiency and consistency of the software catalog by standardizing and automating processes across different tools. These rules help in unifying entity representations from various data sources and ensuring cross-tool uniformity. Automation Rules can be configured to automatically link, map, and populate key assets, making the catalog richer and more accurate as more plugins are installed. {% embed url="" %} ## Use Cases * **Unified Entity Representation:** Different perspectives from various tools are aggregated into cohesive entities, simplifying management and ensuring consistency. * **Cross-Tool Standardization:** Automation rules help standardize entities like pull requests, issues, and services across different platforms, maintaining uniformity and clarity. * **Enhanced Data Integration:** As plugins are installed, automation rules enrich the catalog with detailed and accurate information from multiple sources, improving the overall data quality and usability. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.rely.io/plugins-and-automation/automation-rules/overview-and-use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.