Integrations

Integrations connect Herald to the systems your team already uses: documentation, customer conversations, code, incident tooling, observability platforms, CI systems, and databases. They give your agent the context and read-oriented access it needs to answer questions, investigate issues, and understand how your environment behaves in practice.

Use the integration-specific pages in this section for setup details, required credentials, and configuration notes.

How integrations work

Herald uses integrations in two main ways:

1. Knowledge sources ingest content such as docs, tickets, Slack threads, repository information, and uploaded files. This helps the agent answer questions with the same context your team would normally search for manually.
2. SRE tools provide live, read-oriented access to operational systems such as logs, metrics, traces, incidents, builds, and databases. This helps the agent investigate current issues without requiring you to copy and paste evidence from each tool.

Some integrations do both. For example, an integration may add background knowledge while also giving the agent a tool it can query during an investigation.

Add an integration

To add an integration:

1. Open your agent in the Herald dashboard.
2. Go to Data.
3. Click Add data source.
4. Choose the integration you want to connect.
5. Provide the required credentials, scopes, and connection details.
6. Authorize Herald when prompted.

After you save the integration, it appears in the Data table. Open an integration from that table to check its status, view ingestion progress when applicable, and run available actions.

Start with your incident workflow

If you are setting up Herald for the first time, start with the systems your on-call engineers check most often: observability data, incident history, runbooks, code, deployment context, and team conversations. This gives the agent enough context to connect symptoms, recent changes, and past fixes during an investigation.

Configuration basics

Most integrations ask for a small set of values:

1. Name: A label for the connection in Herald.
2. Credentials: API keys, tokens, service account keys, OAuth authorization, or cloud account details, depending on the service.
3. Scope: The repositories, projects, sites, channels, workspaces, databases, clusters, or URLs Herald should access.
4. Instructions: Optional guidance that tells the agent how to use the integration, such as which environments to prioritize or which indexes to avoid.
5. Update schedule: For integrations that ingest data, Herald uses a default schedule. You can adjust the schedule from advanced configuration where available.

Use the narrowest practical scope and read-only credentials whenever possible. Herald only needs access to the data required for your support, engineering, and incident response workflows.

Update data on demand

Sometimes data needs to be refreshed between scheduled ingestion jobs. To update an integration manually, open it from the Data table and click Run now.

Missing an integration?

Herald is always adding new integrations. If there is a system you want to connect that is not listed in this section, please reach out.