Skip to main content

Sentry

This connector captures data from Sentry into Flow collections.

It is available for use in the Flow web application. For local development or open-source workflows, ghcr.io/estuary/source-sentry:dev provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.

Supported data resources

The following data resources are supported through the Sentry APIs:

By default, each resource is mapped to a Flow collection through a separate binding.

Prerequisites

To set up the Sentry source connector, you'll need a Sentry auth token and the organization slug.

Configuration

You configure connectors either in the Flow web app, or by directly editing the catalog specification files. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Sentry source connector.

Properties

Endpoint

PropertyTitleDescriptionTypeRequired/Default
/credentials/credentials_titleCredentialsName of the credentials setstringRequired
/credentials/access_tokenAccess TokenSentry auth token.stringRequired
/organizationOrganizationThe slug of the organization.stringRequired
/start_dateStart DateThe date from which you'd like to replicate data for Sentry API, in the format YYYY-MM-DDT00:00:00Z. All data generated after this date will be replicated.string7 days before the present
/advanced/window_sizeWindow SizeDate window size for the issues backfill in ISO 8601 format. ex: P30D means 30 days, PT6H means 6 hours. If you have a significant amount of isssues data to backfill, smaller window sizes will allow the connector to checkpoint its progress more frequently.stringP30D

Bindings

PropertyTitleDescriptionTypeRequired/Default
/nameData resourceName of the data resource.stringRequired
/intervalIntervalInterval between data syncsstringPT5M

Sample

captures:
${PREFIX}/${CAPTURE_NAME}:
endpoint:
connector:
image: ghcr.io/estuary/source-sentry:dev
config:
credentials:
credentials_title: Private App Credentials
access_token: <your auth token>
organization: <your organization>
start_date: "2025-08-14T00:00:00Z"
advanced:
window_size: P10D
bindings:
- resource:
name: Issues
interval: PT5M
target: ${PREFIX}/Issues