---
title: Add a Push source
slug: '1546'
canonical_url: https://docs.coveo.com/en/1546/
collection: index-content
source_format: adoc
---
# Add a Push source
Coveo has dedicated [connectors](https://docs.coveo.com/en/2734/) for many web and on-premises systems, letting you quickly make application content searchable.
See the [connector directory](https://docs.coveo.com/en/1702/) for the full list.
However, you may want to [index](https://docs.coveo.com/en/204/) the content of applications that don't have a dedicated connector.
In such cases, the Push [source](https://docs.coveo.com/en/246/) is one of the [generic sources](https://docs.coveo.com/en/1702#generic-connectors) to consider for making the desired content searchable with Coveo.
For example, let's say you have an on-premises content management system (CMS) developed in-house.
With a push approach, one of your developers could create a crawler to retrieve this content and push it to your Coveo organization using the [Push API](https://docs.coveo.com/en/68/).
As the name suggests, this indexing approach involves only outbound requests from your infrastructure, with no inbound requests from the [Coveo Platform](https://docs.coveo.com/en/186/).
But before pushing content to your [Coveo organization](https://docs.coveo.com/en/185/), you must create a Push source to receive the content.
**Architecture diagram of Coveo's push indexing components**
Details
The following diagram shows the main interactions between a custom crawler, the Push API, the indexing pipeline, a Push source, and the other components involved in this process.
