# What happens when you install a Plugin?

## **Integration with Your Engineering Stack**

Rely.io seamlessly integrates with your engineering stack through plugins, each enhancing the platform with specific functionalities. Begin your Rely.io journey by using these plugins to populate your software catalog with services, cloud resources, and more.

For instructions on how to setup your first plugin check our [getting started](/getting-started-guide.md) guide for a basic starting point, however if you want to know further check [self-hosting a plugin](/plugins-and-automation/self-hosting-plugins-using-galaxy.md) and the [plugins installations guides](/plugins-and-automation/plugin-installation-guides.md). 

If you are curious about what happens *under-the-hood* when installing a plugin continue reading*.*

## **Behind-the-Scenes**

* **Data Model Expansion:** Installing a plugin triggers an expansion of your [data model](/basic-concepts/data-model.md) within [Rely.io](http://Rely.io). This expanded model can accurately represent and display entities related to the plugin's data source.
* **Mass Discovery Run:** Post-setup, Rely.io initiates a mass discovery run to query the data source, ingesting entities based on the assets you selected. This ensures your Rely.io catalog mirrors the external data source accurately.
* **Synchronization:** Rely uses webhooks for real-time updates from your data sources, ensuring your catalog is up-to-date. For plugins without webhook support, Rely.io schedules periodic discovery runs to keep your catalog synchronized.
* **Automation Rules:** Once a plugin is installed, [Rely.io](https://rely.io) automatically creates automation rules to link, map, and auto-populate your key assets (like services and resources) based on the data provided by the plugin’s data source. 
  * For example, installing a Git provider plugin means repositories identified during the discovery phase will automatically create service entities in your catalog. 
  * These entities will be enriched with vital information such as the code languages, repository links, README content, etc. 
  * As more plugins are installed and more automation rules created, your catalog becomes more  detailed enhancing your understanding and management of your tech ecosystem.


---

# Agent Instructions: 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.rely.io/plugins-and-automation/what-happens-when-you-install-a-plugin.md?ask=<question>
```

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.