# Push remote content from an external source

Using [remote content](/docs/platform/project/remote-content/remote-content), you can use content from an external source in your Redocly project.
Typically, users fetch content from a public URL, or integrate their Git repository with Redocly.

However, sometimes Redocly cannot be configured to access the remote content source.
In that situation, you can push content updates to your Redocly project when another content source changes.

## Add a remote to push content to

To set up a remote content folder for pushing:

1. In the file tree, select the folder to which you want to add the remote content folder.
  You can also click on the empty space to select the root directory.
2. Select **+ > New remote folder > Add from CI/CD**.
3. Enter name for the new remote content folder and press Enter or Return key.
4. Pick the platform that you will be pushing from to get the relevant fields displayed.
5. Add a list of files to be included when pushing.
6. Complete the other fields for the platform you are using.
7. Copy the provided code snippet.
  For users of our GitHub application, a GitHub Actions workflow is provided.
  For other platforms or GitHub users not using the application, a CLI command is presented that you can run in your CI/CD process.
  In both cases, all the variables you need are pre-filled.

## Get your API key

Authentication is required to push from another platform to Redocly, and this is done using an API key.
To get the value and set it up for use in the CI/CD platform:

1. Get your personal or organization API key by visiting your organization dashboard and selecting **Access** > **API keys** in the navigation menu on the left side of the page.
2. Add an environment variable named `REDOCLY_AUTHORIZATION` with the value of your API key to your CI/CD platform.
3. Use this variable with the command or workflow you copied in the previous step.

## Push changes

Each push has a maximum request size of 500 MiB.
The limit includes all files, form fields, and multipart overhead.
The Redocly platform returns a HTTP 413 error when a push exceeds this limit.
Reduce the files in the push before you retry.

To push changes to Redocly:

1. Make a change to the remote content source.
2. Check that the CI/CD steps you set up earlier in this guide ran as expected.
3. Visit Redocly to review the new deployment.

**Branch protection**

Pushes from CI/CD are subject to your Git provider's branch protection rules.
For example, if you have enabled "Require a pull request before merging" for your default branch, a push to that branch fails to merge automatically.

## Resources

- **[Add remote files with one-way sync](/docs/platform/project/remote-content)** - Explore different methods for integrating various external content sources into your Redocly projects
- **[Remote content](/docs/platform/project/remote-content/remote-content)** - Understand remote content fundamentals including sync mechanisms, folder paths, and auto-merge capabilities
- **[Push remote content using GitHub Actions](/docs/platform/project/remote-content/reunite-push-action)** - Configure the platform push GitHub Action for automated content synchronization and deployment workflows
- **[CLI push command](https://redocly.com/docs/cli/commands/push)** - Complete reference for the Redocly CLI push command with usage examples and configuration options