---
title: How to update Integrations documentation
description: Integrations documentation lives in the elastic/integrations repository and follows a specific workflow that differs from other Elastic documentation...
url: https://www.elastic.co/elastic/docs-builder/docs/3028/contribute-docs/how-to/update-integrations-docs
applies_to:
- Elastic Cloud Serverless: Generally available
- Elastic Stack: Generally available
---
# How to update Integrations documentation
Integrations documentation lives in the [elastic/integrations](https://github.com/elastic/integrations) repository and follows a specific workflow that differs from other Elastic documentation. Changes to integration docs require updating source files, bumping versions, and waiting for the package to be published to the Elastic Package Registry (EPR) before they appear on the docs site.
## Prerequisites
Before you start, make sure you have:
- Write access to the [elastic/integrations](https://github.com/elastic/integrations) repository (for Elastic contributors).
- The [`elastic-package`](https://github.com/elastic/elastic-package) tool installed locally.
## Update the docs
Create a branch with the pattern `docs-enhancement/{desired_branch_name}`:
```bash
git checkout -b docs-enhancement/my-docs-update
```
Edit the source file at `packages/{package}/docs/README.md` or `packages/{package}/_dev/build/docs/README.md`.
Other structures might exist. Most packages use a single README.md. A small minority use a multi-file structure, for example, one file per cloud service or component.If your package has doc files in both `packages/{package}/docs/README.md` _and_ `packages/{package}/_dev/build/docs/README.md`, ensure you edit the source file at `packages/{package}/_dev/build/docs/README.md`.
Commit and push your changes to the remote repository:
```bash
git add .
git commit -m "docs: update {package} documentation"
git push -u origin docs-enhancement/my-docs-update
```
Create a PR to the upstream [elastic/integrations](https://github.com/elastic/integrations) repository.Wait for the **Documentation edit helper** check to complete. This check generates the commands you'll need in the next step.
1. In your PR, select the **Documentation edit helper** check.
2. Select **Summary** in the top left.
3. Copy the commands from the **Documentation follow-up** panel. The commands look similar to this:
```bash
for pkg in docker; do
cd packages/$pkg
elastic-package changelog add --type enhancement --description "Improve documentation" --link "https://github.com/elastic/integrations/pull/123456" --next minor
elastic-package build
cd ../..
done
git add -u
git commit -m "docs: update changelogs and build documentation"
git push
```
4. Go back to your editor, and from the integrations repository root folder, paste and run the copied commands.
These commands:
- Build the generated `packages/{package}/docs/README.md` file.
- Update `changelog.yml` with the new entry.
- Update `manifest.yml` with the new version.
If you need to make subsequent edits to your PR, save your changes, then re-run the `elastic-package build` command from the package's root folder (not the integrations root folder) before you push your commits. This ensures the `packages/{package}/docs/README.md` file is updated with your new changes.
Go back to your PR, request a code owner review, and merge it once approved.
## After merging: When changes appear
After your PR is merged, changes don't appear immediately on the docs site. The process involves several automated steps:
1. **Package publication**: The package is published to the [Elastic Package Registry (EPR)](https://github.com/elastic/package-registry). You'll know this is complete when a bot comments on your PR with a message like:
> Package {package_name} - {version} containing this change is available at [https://epr.elastic.co/package/{package_name}/{version}](https://epr.elastic.co/package/{package_name}/{version})
2. **Docs sync**: A scheduled job in the [elastic/integration-docs](https://github.com/elastic/integration-docs) repository pulls the latest packages from EPR and opens an automated PR. This job runs once a day.
3. **Docs build**: Once the automated PR is merged, changes propagate to the docs site.
If you need changes to appear sooner, you can manually trigger the [update-docs workflow](https://github.com/elastic/integration-docs/actions/workflows/run-update-docs.yml) in the integration-docs repository.
## Troubleshooting
### Changes aren't appearing after merge
If your changes don't appear on the docs site after following these steps:
1. **Check for the EPR bot comment**: Look for the bot comment in your PR confirming the package was published to EPR. If you don't see it, the package hasn't been published yet.
2. **Verify the version was bumped**: Ensure your PR included updates to both `changelog.yml` and `manifest.yml`. Without these updates, a new package version won't be published.
3. **Check the integration-docs repository**: Look at recent automated update PRs in the integration-docs repository. If they're failing, your changes won't be pulled until the issues are resolved.
4. **Check version compatibility**: Check if the integration's `manifest.yml` specifies a Kibana version that hasn't been released yet. For example, if `^9.3.0` before 9.3 is released, the docs won't appear until that version is live.
### The edit helper check is missing
If you can't find the edit helper check on your PR, ensure your branch name follows the `docs-enhancement/` pattern.
### Build failures in integration-docs
Sometimes the automated PR in integration-docs fails due to new integrations that need to be added to `nav.yaml`. These failures block all docs updates until resolved. If you notice this, reach out to the docs team for assistance.