> 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/basic-concepts/actions-and-automations.md).

# Actions and Automations

Rely.io focuses on automating and simplifying developer workflows through the use of two powerful tools:

* Automations
* Self-Service Actions

## Automations

Data can be mapped from [Plugin Blueprint](/basic-concepts/user-blueprints-vs-plugin-blueprints.md#plugin-blueprints) entities to [User Blueprint](/basic-concepts/user-blueprints-vs-plugin-blueprints.md#user-blueprints) entities via automation rules. 

This mapping creates a dynamic abstraction layer, allowing data from various sources to be filtered, manipulated, standardized, and centralized according to your needs. Automation Rules serve two main purposes:

1. Unified Entity Representation: Different tools like git providers, incident management tools, and observability platforms represent a "Service" in various ways. Automation rules and user blueprints let you aggregate these diverse perspectives into a single, cohesive "Service" entity. This entity contains only what matters most from each source and reflects your organization's operational context.
2. Standardizing Cross-Tool Entities: For example, pull requests and merge requests from both GitHub and GitLab can be standardized into a unified format, as can issues from both Jira and Linear. This standardization enables large organizations to maintain uniformity and clarity in their Internal Developer Platform (IDP) across different team processes and toolsets.

{% hint style="info" %}
Rely.io takes a proactive approach by offering **pre-configured automation rules** for common use cases, which are automatically included when you install certain plugins. 

These default automation rules leverage:

* [The specific data model associated with each plugin](/basic-concepts/user-blueprints-vs-plugin-blueprints.md#plugin-blueprints)
* [The out-of-the-box data model Rely offers when first creating your organization](/basic-concepts/data-model.md#default-data-model)

These rules are designed to streamline processes and ensure seamless integration of plugin data with the most common [user blueprints](/basic-concepts/user-blueprints-vs-plugin-blueprints.md#user-blueprints). 
{% endhint %}

## Self-Service Actions


---

# 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/basic-concepts/actions-and-automations.md?ask=<question>&goal=<endgoal>
```

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