Skip to main content

Sentry Feeds

Sentry is an application monitoring platform that captures errors, crashes, and performance data from software in production, helping engineering teams find, triage, and resolve issues faster. The Sentry Feeds connector is a source-only ELT connector that ingests Sentry data as a set of feeds. Select from the available organization data types — projects, teams, issues, and releases — and Nexla loads each selected object as its own feed on a schedule, using either a full refresh or an incremental sync. For a REST-endpoint-oriented Sentry connector, see the Sentry API connector.

Sentry Feeds icon

Power end-to-end data operations for your Sentry Feeds API with Nexla. Our bi-directional Sentry Feeds connector is purpose-built for Sentry Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Sentry Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Sentry Feeds workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

The Sentry Feeds connector authenticates with a Sentry authentication token sent as a bearer token in the Authorization header. Before creating a credential in Nexla, generate a token in Sentry and note your organization slug and Sentry instance URL.

Generate a Sentry authentication token​

Sentry supports both user (personal) authentication tokens and organization authentication tokens. Either can be used, as long as the token carries read scopes for the data you plan to ingest.

To create a user authentication token:

  1. Sign in to Sentry with an account that has access to the organization you want to ingest from.

  2. Open User Settings, then navigate to the Auth Tokens (Personal Tokens) page. In Sentry's self-hosted and legacy interfaces this appears under Settings > Account > API > Auth Tokens.

  3. Create a new token and assign the read scopes required for your feeds, such as org:read, project:read, and event:read.

  4. Copy the generated token immediately and store it securely. The token grants the same access to Sentry data as the scopes you assigned.

Organization authentication tokens are created through an internal integration in your organization settings and are also supported for both Sentry Cloud (sentry.io) and self-hosted instances.

Identify your organization slug and instance URL​

  • Organization slug: The short identifier for your organization, visible in Sentry URLs (for example, https://sentry.io/organizations/my-organization/). You will enter this when configuring the source.

  • Instance URL: Use sentry.io for Sentry Cloud. For a self-hosted Sentry deployment, use the hostname of your own instance.

Treat the Sentry authentication token as a sensitive secret. Grant only the read scopes needed for the feeds you plan to ingest, and rotate the token if it is exposed.

For more information, see the Sentry API authentication documentation and the Sentry API reference.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Sentry Instance URLYesNoThe URL of your Sentry instance
Authentication TokenYesYesYour Sentry authentication token with appropriate scopes (org:read, project:read, event:read, etc.)

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. Use them to identify the Sentry organization, instance, or access level represented by this credential.

  3. Enter the hostname of your Sentry instance in the Sentry Instance URL field. Use sentry.io for Sentry Cloud, or the hostname of your self-hosted deployment.

  4. Enter the Sentry authentication token in the Authentication Token field. Nexla sends this token to Sentry as a bearer token in the Authorization header when ingesting feeds.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Sentry Feeds flows.

Use as a data source​

How This Connector Works​

The Sentry Feeds connector is a source-only, multi-object ELT connector. Rather than configuring one endpoint at a time, you select the Sentry data types you want and Nexla ingests each selected object as its own feed against the Sentry organization API.

  • Discovery: When you create the source, Nexla presents the Sentry data types available from the connector for selection.

  • Data loading strategy: Each feed is loaded using one of two strategies. Full Refresh reads the complete current set of records for the object on every run. Incremental Sync reads only records changed since a lookback point, filtering on Sentry's lastSeen value. The id field is used as the primary key to uniquely identify records within each feed.

  • Parallel ingestion: Selected feeds are ingested in parallel, so a single source can pull multiple Sentry objects on the same schedule. Sentry list responses are paginated, and Nexla follows the pagination Link header automatically while reading each feed.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Sentry Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to Sentry and click Next; or, create a new Sentry Feeds credential for use in this flow.

Select the Objects to Ingest​

After authenticating, Nexla lists the Sentry data types available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed.

  • Projects — Projects in your Sentry organization.
  • Teams — Teams in your Sentry organization.
  • Issues — Grouped errors and problems tracked in your organization.
  • Releases — Releases registered against your organization's projects.

Configure the Feed​

The following options control how each feed is loaded. Provide them during source configuration.

  • Data Loading Strategy — Choose Full Refresh to read the complete set of records on every run, or Incremental Sync to read only records changed since the lookback point.

  • Organization Slug (required) — The slug or ID of your Sentry organization (for example, my-organization).

  • Incremental Syncs: Lookback Time — For incremental sync, the earliest point from which changes should be captured, in ISO 8601 format (for example, 2024-01-01T00:00:00Z).

  • Page Size — Number of records per API request (maximum 100).

  • Sort Order — Sort order for results: Date, Priority, Frequency, or New.

The following optional filters apply where the selected object supports them:

  • Statistics Period — Time period for statistics: Last 24 Hours, Last 14 Days, Last 30 Days, Last 90 Days, or No Stats.
  • Environment — Filter results by environment (for example, production).
  • Issue Query Filter — Additional query filters for issues (for example, is:unresolved, is:assigned, level:error).
  • Date From — Start date for data extraction, in ISO format.
  • Project Slug — The slug of a specific project, required only for project-scoped feeds.

Incremental Sync filters on Sentry's lastSeen value, so it is best suited to objects that track a last-seen timestamp, such as issues. For reference-style objects, use Full Refresh to capture the complete current set on each run.

Schedule and Activate​

  • Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected feed is loaded using its configured strategy.

Reference​

For object schemas, field definitions, scopes, and additional detail on each Sentry endpoint, see the Sentry API reference.