Connecting Sentry to Landfall

Sentry is usually the first system to know an incident exists — most real incidents start life as an application exception, not an infrastructure alarm. This guide covers three things: creating a scoped auth token and pasting it in, what the investigator agent can read once connected, and — under its own section below — wiring Sentry's issue-alert webhook so it opens a Landfall war room automatically.

What you'll need

• A Sentry account, and to know your organization's slug (shown in the URL after sign-in, e.g. sentry.io/organizations/<org-slug>/).
• An admin on your Landfall organization, to save the connection under Settings → Integrations.
• If you self-host Sentry: your instance's base URL — Landfall calls the same /api/0/… surface on any origin.

1. Create a Sentry auth token

Landfall only ever reads from Sentry: it verifies the token is alive and then reads issues/events when an incident is being investigated. An Internal Integration's own token is the narrowest option — scoped to one internal integration you create and name, rather than a broad personal auth token. Give it Read access to Issue & Event and Read access to Organization; nothing else is needed.

1. Sentry → Settings → Developer Settings → New Internal Integration

   Name it something you'll recognize later (e.g. landfall-integration).

   sentry.io/settings/<org-slug>/developer-settings/new-internal/

   🖼Sentry's New Internal Integration form, named and with Issue & Event / Organization permissions set to Read.

2. Permissions: Issue & Event → Read, Organization → Read

   Both are read-level, nothing more. Landfall never resolves, assigns, or otherwise mutates a Sentry issue through this token — the read plugin's operations are structurally read-only regardless of what a broader token could do.

3. Save, then copy the token

   Sentry shows the token once, on the integration's detail page after saving. Copy it now: you'll paste it straight into Landfall in the next step.

   sentry.io/settings/<org-slug>/developer-settings/landfall-integration/

   🖼Sentry showing a newly created Internal Integration's token value, with a copy-to-clipboard control.

2. Add it to Landfall

In Landfall, open Settings → Integrations → Sentry for your organization. It asks for the token, your organization slug, and two optional fields: a default project slug (used when a read doesn't name one explicitly) and a self-hosted API base URL override.

1. Paste the token and organization slug, then Test connection

   Landfall calls Sentry's own organization-details API with the token before saving anything — a token that can't authenticate, or an organization slug Sentry doesn't recognize, is refused outright rather than stored as "configured but unverified."

   Settings → Integrations → Sentry

   🖼Landfall's Sentry integration panel showing a green connected status and the message Sentry organization verified.

2. Save integration

   Sentry now shows Configured alongside your organization's other connectors.

3. Triggering Landfall from Sentry

Connecting Sentry (above) lets the investigator agent read your issues and events during an investigation. It's a separate step to have a Sentry issue-alert open that investigation in the first place — see Triggering Integrations → Sentry for the webhook setup, the exact body Sentry sends, and worked examples. The two are independent; most teams eventually set up both.

Reference