# Integrations for Building your Catalog

> Manage HTTP, AWS, and other integrations that power catalog data sources and workflow source nodes.

*Published: 2026-04-09*


## Overview

**Integrations** are reusable connection definitions—credentials, base URLs, and provider-specific settings—that **data sources** use when fetching data. 

They are the same integration system used across Roadie’s catalog tooling, so you configure them once and reference them from multiple sources or workflows.

From the **Integrations** overview you can browse, search, and filter integrations; create new ones; and edit or remove existing definitions (subject to permissions).

![integration-list(./integration-list.webp)]

## How they fit the pipeline

1. Create an **integration** for the system you need to reach (for example, an HTTP API or AWS API).
2. Use that integration in a **[data source](/docs/catalog/building-your-catalog/data-sources/)** so scheduled syncs can write objects into the datastore.

For HTTP-style access patterns elsewhere in Roadie (proxies, authenticated requests from plugins), see also the general [HTTP integration](/docs/integrations/http/) documentation. Integrations used when Building your Catalog are configured in the dedicated **Integrations** UI for data sources and workflows.

![integration-new(./integration-new.webp)]

## Permissions

Creating, updating, and deleting integrations is gated by integration permissions. Restrict these to administrators or platform engineers who are allowed to manage outbound credentials and endpoints.

## Further reading

- [Building your Catalog — overview](/docs/catalog/building-your-catalog/)
- [Data sources](/docs/catalog/building-your-catalog/data-sources/)
- [Workflows to create entities](/docs/catalog/building-your-catalog/workflows/)
- [HTTP integration](/docs/integrations/http/)