> 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/getting-started-guide/add-your-first-plugin.md).

# Add your first plugin

Let's kickstart your [Rely.io](http://Rely.io) journey by populating your software catalog. With our plugins, you can seamlessly import services, cloud resources, and much more into your developer portal.

## **Create your first plugin**

Navigate to the [Plugins Page](https://webapp.rely.io/data-model/datasources) by clicking the **Portal Builder** menu on the bottom left and then select **Plugins.** \
\
Initially, you'll see our built-in plugins for the [Rely.io](http://Rely.io) API and the Self-Service Agent. These are designed for managing entities programmatically and execute Self-Service actions.

<figure><img src="/files/GlhkmV73lSabLJSqwCXX" alt=""><figcaption></figcaption></figure>

To create your first plugin click on **Add Data Source** and select from the available options.&#x20;

<figure><img src="/files/VMhfgq4NKu05EexGEg19" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Starting with your Git provider (Github, GitLab or Bitbucket) is recommended, as it populates your [service catalog](https://webapp.rely.io/software-catalog/service/list) efficiently - but it is not the only option.&#x20;

Still, for the purpose of this *getting started* guide we will use GitLab.
{% endhint %}

To complete the setup for the selected plugin you need to fill-in the mandatory fields. These change depending on the plugin. Follow the installation steps.&#x20;

<figure><img src="/files/GvB0S0ajmN1MvwgTRbC2" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
During this process, you may be redirected to the plugin platform for authorization or asked to input an access token, depending on the plugin.&#x20;
{% endhint %}

After that, select the assets you wish to import (such as repositories or issues) and click the **Submit** button.

<figure><img src="/files/5ISa8uwh8MoOAk57OArT" alt=""><figcaption></figcaption></figure>

**And that's it!** The initial discovery run can take a few minutes to complete. As you await the results, this is the perfect opportunity to dive deeper into how you can utilize the data that plugins provide, by exploring the core features of the software catalog.

If you are curious about what happens *under-the-hood* when you add new plugins check out "[*What happens when you install a plugin?*](/plugins-and-automation/what-happens-when-you-install-a-plugin.md#behind-the-scenes)*"*.

Next, we'll [import services into the service catalog](/getting-started-guide/import-services-into-the-service-catalog.md).


---

# 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/getting-started-guide/add-your-first-plugin.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.