Sentry

Track errors, monitor performance, and manage releases with Sentry.

Detail	Value
Category	Dev Tools
Base URL	https://sentry.io/api/0
Authentication	Bearer Token
Endpoints	5
Connector key	sentry

Using Sentry in a workflow

1. Go to Connections and click New Connection.
2. Pick Sentry from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /organizations/{organization_slug}/issues/	List issues for an organization
GET /organizations/{organization_slug}/issues/{issue_id}/	Get an issue
GET /organizations/{organization_slug}/issues/{issue_id}/events/	List events for an issue
GET /projects/{organization_slug}/{project_slug}/	Get project details
GET /organizations/{organization_slug}/releases/	List releases

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /organizations/{organization_slug}/issues/

List issues for an organization

Detail	Value
Operation ID	devtools.listIssues
Method	GET
Path	/organizations/{organization_slug}/issues/

Parameters

Name	Location	Type	Required
organization_slug	path	string	Yes
query	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listIssues.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sentry API reference.

GET /organizations/{organization_slug}/issues/{issue_id}/

Get an issue

Detail	Value
Operation ID	devtools.getIssue
Method	GET
Path	/organizations/{organization_slug}/issues/{issue_id}/

Parameters

Name	Location	Type	Required
organization_slug	path	string	Yes
issue_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.getIssue.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sentry API reference.

GET /organizations/{organization_slug}/issues/{issue_id}/events/

List events for an issue

Detail	Value
Operation ID	devtools.listIssueEvents
Method	GET
Path	/organizations/{organization_slug}/issues/{issue_id}/events/

Parameters

Name	Location	Type	Required
organization_slug	path	string	Yes
issue_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listIssueEvents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sentry API reference.

GET /projects/{organization_slug}/{project_slug}/

Get project details

Detail	Value
Operation ID	devtools.getProject
Method	GET
Path	/projects/{organization_slug}/{project_slug}/

Parameters

Name	Location	Type	Required
organization_slug	path	string	Yes
project_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.getProject.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sentry API reference.

GET /organizations/{organization_slug}/releases/

List releases

Detail	Value
Operation ID	devtools.listReleases
Method	GET
Path	/organizations/{organization_slug}/releases/

Parameters

Name	Location	Type	Required
organization_slug	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Sentry connection from the Connection dropdown.
3. In the Operation dropdown, select devtools.listReleases.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Sentry API reference.