CI/CD Quality Gate for Sentry Artifact Verification - n8n Workflow

• DevOps Engineers and CI/CD Specialists needing automated artifact verification.


• Teams using Sentry for error monitoring and requiring guaranteed symbol/mapping file uploads.


• Developers looking for custom quality gates within their continuous integration pipeline using an n8n node approach.


• Users searching for practical n8n templates to bridge development tools like GitHub and Sentry.

Maintaining high code quality and ensuring proper crash reporting requires validating that critical debugging artifacts, such as dSYM or ProGuard mapping files, are correctly uploaded to Sentry after every build. Manually checking this process is tedious and prone to error.

This specialized n8n workflow solves this by acting as a CI/CD Quality Gate. It automatically starts with an n8n trigger (a Git push event), queries the Sentry API for the release files, applies custom verification logic (using an n8n node for code scripting), and then updates the commit status on GitHub. By leveraging this n8n template, development teams gain immediate feedback on artifact completeness, preventing deployment errors caused by missing symbolic files and ensuring reliable crash analysis.

This automation provides a critical check in the development pipeline:

1. Initiation: The process starts with the GithubPushTrigger n8n trigger, which activates upon a push event to a configured repository. It captures the crucial commit SHA and repository details.


2. Sentry Release Lookup: The first HTTP Request node (Check Sentry Artifacts Releases) queries the Sentry API to retrieve all releases associated with the project, using data derived from the n8n workflow input to identify the specific target release version.


3. Artifact File Listing: The next HTTP Request n8n node (Check Sentry Artifacts files) uses the identified release version to fetch a detailed list of all artifacts uploaded to Sentry for that release.


4. Verification Logic: The Verify Artifacts n8n node (Code node) executes custom JavaScript logic. This logic checks the returned list of filenames for key patterns: it passes if a .dSYM file is found, OR if both proguard.txt and mapping.txt files are present. It outputs a status ('success' or 'failure') based on this analysis.


5. Quality Gate Enforcement: The Artifacts Validation and Get Repository Data Code n8n node acts as the flow control gate. It only allows the n8n workflow to proceed if the status from the previous step is 'success'. If verification fails, the workflow terminates, effectively blocking the associated Pull Request.


6. Status Update: If the artifacts are complete, the final Update Status HTTP Request n8n node posts a 'success' status back to the GitHub Commit Statuses API, confirming the completion of the artifact gate check.

To implement this powerful n8n workflow, follow these steps:

1. Import: Download the provided JSON data and import it directly into your n8n instance using the 'New' -> 'Import from JSON' option.


2. Credentials Setup: You will need two types of credentials for the n8n template:

1. Configure Trigger: In the GithubPushTrigger n8n node, specify your repository owner and repository name.


2. Configure Sentry URLs: In the Check Sentry Artifacts Releases and Check Sentry Artifacts files n8n nodes, replace orgslug and projslug within the URLs with your actual Sentry organization and project identifier slugs.

This n8n workflow leverages several specialized n8n node types to achieve its functionality:

GithubPushTrigger (n8n trigger):
Function: Starts the n8n workflow execution whenever code is pushed to the configured repository branch.
Key Configuration: Configured to listen for push events and requires a GitHub API credential.
Check Sentry Artifacts Releases (HTTP Request n8n node):
Function: Retrieves a list of Sentry releases to find the one matching the current commit context.
Key Configuration: Uses Sentry API credentials and targets the /api/0/projects/{org}/{proj}/releases/ endpoint.
Check Sentry Artifacts files (HTTP Request n8n node):
Function: Fetches the list of all files uploaded for the specific release, using dynamic expressions ({{ $json.version }}) to interpolate the release identifier.
Key Configuration: Requires Sentry API credentials; targets the /api/0/projects/{org}/{proj}/releases/{{ version }}/files/ endpoint.
Verify Artifacts (Code n8n node):
Function: Contains the core verification business logic. It checks if required files (dSYM, proguard.txt, mapping.txt) are present using Regular Expressions against filenames.
Key Configuration: Custom JavaScript logic defining the success criteria for artifact completeness.
Artifacts Validation and Get Repository Data (Code n8n node):
Function: Acts as the CI gate. It retrieves necessary GitHub data (SHA, repo name) and halts the n8n workflow if the prior artifact verification failed.
Key Configuration: Uses conditional return (if ($input.first().json.status === 'success')) to control subsequent flow.
Update Status (HTTP Request n8n node):
Function: Posts the final verification result back to GitHub as a commit status, signaling the gate passed successfully.
Key Configuration: HTTP POST request to the GitHub Commit Statuses API using dynamic parameters for the SHA and repository details.