Automate Sentry Releases Creation and Retrieval with n8n

What this workflow does

This workflow helps create a new release in Sentry.io and then fetches all existing releases automatically.

It solves the problem of manually adding and checking releases in Sentry, which often wastes time and causes mistakes.

The result is a fast, error-free way to manage releases that saves about 10 minutes each time.

Who should use this workflow

Developers or release managers who handle many projects and publish frequent releases in Sentry.io.

It suits those wanting to avoid repetitive manual tasks and reduce errors in release versioning.

Tools and services used

• n8n: The automation platform where this workflow runs.
• Sentry.io API: Used to create releases and get release data.
• Sentry API Key: Required for authentication with the Sentry platform.

Inputs, Processing steps, and Outputs

Inputs

• Manual trigger from the user to start the workflow.
• Release version number to create a new release.
• Sentry organization slug and project list to target specific releases.
• Valid API credentials for Sentry access.

Processing steps

• The workflow starts when the user manually triggers it.
• The workflow creates a new release in Sentry with the specified version.
• It then requests all existing releases from the same organization.
• The workflow fetches and prepares the full list of releases for viewing.

Outputs

• A new release appears in Sentry with the correct version.
• A list of all current releases from the organization is returned.
• Data shown in the n8n execution panel for confirmation.

Beginner step-by-step: How to use this workflow in n8n

Download and import the workflow

1. Download the workflow file using the Download button on this page.
2. In the n8n editor, click on “Import from File” and select the downloaded workflow file.

Configure credentials and settings

3. Add your Sentry API Key in the credentials section.
4. Update the Organization Slug and Projects fields in the Sentry nodes to match your Sentry account.
5. Change the release version number in the create release node if needed.

Test and activate

6. Run the workflow once manually using the Manual Trigger node.
7. Check the execution panel to ensure a release is created and releases list is fetched.
8. Activate the workflow by toggling it to “Active” to use it in production.

Consider replacing the Manual Trigger with a Webhook node for automated release creations from your deployment pipelines.

For self hosting n8n, visit this resource.

Customization ideas

• Use expressions to set release versions dynamically instead of hardcoding.
• Filter releases in the “Get All Releases” node by date or other criteria.
• Change the Manual Trigger to Webhook node for integration with CI/CD.

Edge cases and troubleshooting tips

• If authentication fails, check the Sentry API Key permissions and reapply credentials.
• If releases do not show, verify that the “Return All” option is enabled in the release fetch node.
• Ensure nodes are properly connected; missing links can cause the workflow to stop.

Summary of benefits and results

✓ Saves about 10 minutes per release by automating creation and retrieval.

✓ Removes errors caused by manual version input.

✓ Shows full release list immediately after creation.

✓ Supports multiple projects and flexible configurations.

→ Helps developers focus more on coding than release administration.