Skip to main content

Install integrations

Integrations are the backbone of your developer portal. They allow you to ingest data from your tech stack and create a comprehensive software catalog.

Using your prioritized list of tools and platforms required to implement your MVP, install the relevant integrations as per the following steps:

Install pre-built integrations​

If Port offers a pre-built integration for your desired tool, install it to quickly start ingesting data.

Some components will be automatically created in your portal:

  • Default blueprints will be created in your Builder to model the incoming data.
  • Default mapping will be defined to map the incoming data to the blueprint's properties.
Default components

All default components created by pre-built integrations can be fully customized to better fit your needs.


Note that for pre-built integrations, Port offers several installation methods, each with its own syncing mechanism and hosting options (see each integration's documentation for the available options).

Choose the method that best fits your infrastructure and processes.

Set up custom integrations​

If Port does not offer a pre-built integration for your desired tool, you can create a custom integration and ingest data using one of the following methods:

For custom integrations, you will need to:

  • Create custom blueprints in your Builder to model the incoming data.
  • When ingesting data, make sure to map it to the relevant properties in the target blueprint/s.

Create logical connections between blueprints​

Once your software catalog is populated with data from different sources, you can create logical connections between blueprints to define the relationship between them.

This is one of the main strengths of a developer portal - tools in your ecosystem that were once unaware of each other are now part of a catalog that can be used to create new insights and workflows.

For example:

  • Once you connect your Jira issue and Service blueprints, you can create a dashboard widget that tracks and displays the open issues in Jira that are related to a specific service.
  • Once you connect your PageDuty incident and Service blueprints, you can define an automation that notifies the service owner when a new incident is created for their service.

Use relations to define the logical relationships between the blueprints in your portal.

Next step - set up RBAC & ownership​

Once you have installed your desired integrations, proceed to the next step.