Sentry.io n8n integrationAutomate Sentry.io with n8n.

Pulls one event out of a project, addressed by its own ID rather than by the issue it belongs to. The node returns that event as a single item.

• Organization Slug Name or ID: the slug of the organization the events belong to, chosen from the list or set with an expression.
• Project Slug Name or ID: the slug of the project the events belong to, same list-or-expression choice.
• Event ID: either the numeric primary key or the hexadecimal ID as reported by the raven client.

Lists the events recorded for one project and hands them to the next node one item at a time.

• Organization Slug Name or ID: which organization to read from.
• Project Slug Name or ID: which project the events belong to.
• Full: switched on, the payload includes the full event body, stack trace included.
• Return All: on, n8n chains the API pages until everything is in; off, Limit caps how many events come back.

Removes one issue from Sentry, addressed by its ID and nothing else.

• Issue ID: the identifier of the issue, shaped like the 1234 placeholder shown in the field, and often {{ $json.field }} when the value travels from an earlier node.

Reads one issue back from Sentry, so the workflow acts on what Sentry holds right now instead of on a copy captured minutes earlier.

• Issue ID: the identifier Sentry gives the issue, in the 1234 shape the field suggests.

Browses the issues of a project. Leave the search empty and Sentry assumes an implied is:unresolved, which is why this operation is the usual starting point for a triage workflow.

• Organization Slug Name or ID and Project Slug Name or ID: the two slugs that scope the search.
• Query: an optional Sentry structured search query, in the same syntax as the product's search bar.
• Stats Period: the time period of the stats, 24h or 14d.
• Short ID Lookup: opt-in, because looking up short IDs can return an issue belonging to another project.
• Return All and Limit: the full list, or a capped one.

Changes the state of an existing issue from a workflow, which is how Sentry stays in sync with whatever tool the team actually works in.

• Issue ID: the issue to modify.
• Status: the new status, among resolved, resolvedInNextRelease, ignored and unresolved.
• Assigned To: the actor ID or username of the user or team that should own it.
• Is Public: whether the issue is set to public or private.
• Is Bookmarked, Is Subscribed, Has Seen: the user-context flags.

Creates a new organization, the top-level container that everything else in Sentry hangs from.

• Name: required, the name of the organization.
• Agree to Terms: whether you agree to the applicable terms of service and privacy policy of Sentry.io.
• Slug: the unique URL slug; left empty, a slug is generated automatically from the name.

Fetches a single organization from its slug, which is the quickest way to confirm a credential really reaches the account you think it does.

• Organization Slug Name or ID: picked from the dropdown, which n8n fills using the credential, or set with an expression when the slug comes from an earlier node.

Returns the organizations the credential can see, which matters as soon as one token covers several accounts.

• Member: restricts the results to organizations you have membership in.
• Owner: restricts them to the ones you own.
• Return All: every page, or Limit to stop after a given number of organizations.

Edits an organization that already exists, without touching anything it contains.

• Slug Name or ID: this operation names the target field differently from the rest of the node, so look for Slug Name or ID and not the usual organization dropdown.
• Name: the new name of the organization.
• Slug: the new URL slug.

Adds a project under an existing team, so a new service starts reporting into its own space instead of polluting an old one.

• Organization Slug Name or ID: where the project lives.
• Team Slug Name or ID: the slug of the team the project is created for.
• Name: the name for the new project.
• Slug: optional; without it, a slug is generated from the name.

Takes a project out of an organization. Both slugs are required, which is a small safety net: you have to name the organization before you can name what disappears from it.

• Organization Slug Name or ID: the organization the project belongs to.
• Project Slug Name or ID: the slug of the project to delete.

Opens the record of one project and passes it on as a single item.

• Organization Slug Name or ID: the organization the events belong to.
• Project Slug Name or ID: the slug of the project to retrieve.

Enumerates the projects the credential reaches. No slug is required here, which makes it the easiest operation to test a fresh Sentry.io credential with.

• Return All: on, n8n follows every page of projects; off, Limit sets the ceiling.

Adjusts the settings of a project already in place.

• Organization Slug Name or ID and Project Slug Name or ID: the project to update.
• Name and Slug: the new name and the new slug.
• Platform: the new platform for the updated project.
• Team: the new team name.
• Digests Maximum Delay and Digests Minimun Delay: the maximum and minimum interval to digest alerts. The second label carries a typo in the node itself, so do not go looking for a different field.

Registers a release in Sentry, which is what lets the product tie an error back to the version that introduced it.

• Organization Slug Name or ID: the organization the release belongs to.
• Version: a version identifier, a version number or a commit hash.
• URL: a URL pointing to the release, for instance an online interface to the source code.
• Project Names or IDs: a list of project slugs involved in this release.
• Date Released, Commits, Refs: optional.

Drops a release from an organization, addressed by its version identifier.

• Organization Slug Name or ID: the organization the release belongs to.
• Version: the version identifier of the release, the same string that was used to create it.

Looks up a release from its version identifier. Handy as a check before a deploy: if the version already exists in Sentry, the pipeline knows it is about to repeat itself.

• Organization Slug Name or ID: where to look.
• Version: the version identifier of the release.

Walks through the releases of an organization, newest ones included, in one node run.

• Organization Slug Name or ID: the organization the releases belong to.
• Query: creates a starts-with filter on the version, so a naming convention like a product prefix becomes a filter for free.
• Return All: every page of releases; off, Limit caps the list.

Completes a release that already exists, typically because the data arrived after the deploy rather than during it.

• Organization Slug Name or ID and Version: the release to amend.
• Commits and Refs: the commit data, and the start and end commits for each repository included in the release.
• Date Released: when the release actually went live.
• URL and Ref: a URL pointing to the release.

Sentry.io groups people and projects under teams, and this operation adds one from a workflow. The new team lands inside the organization you point at.

• Organization Slug Name or ID: the slug of the organization the team belongs to. Pick it from the dropdown n8n loads, or pass an expression (a small formula that reads the incoming item) such as {{ $json.field }}.
• Name: the name of the team. It is required, so an empty value stops the node.
• Slug: optional, under Additional Fields. Leave it out and Sentry.io generates the slug from the name.

When a squad is dissolved, its team stays behind and keeps showing up in Sentry.io project settings. This operation removes it, and it wants slugs, not the display names you read in the interface.

• Organization Slug Name or ID: the slug of the organization the team belongs to, chosen from the list or supplied as an expression.
• Team Slug Name or ID: the slug of the team to delete. Same dropdown, same fallback to {{ $json.field }} when the value travels from an earlier node.

Pulling one team back into a workflow gives you its record as the node output, which is what you want before deciding to update it or delete it. The lookup goes through the team slug.

• Organization Slug Name or ID: the slug of the organization the team belongs to, from the dropdown or from an expression.
• Team Slug Name or ID: the slug of the team to get. If the slug is wrong the node fails, so read it from a previous step rather than typing it by hand.

An organization accumulates teams faster than anyone documents them. This operation lists the teams of one organization so the rest of the workflow has something to loop over.

• Organization Slug Name or ID: the slug of the organization whose teams should be listed.
• Return All: checked, n8n chains the API pages and brings back every team of the organization.
• Limit: the maximum number of teams returned when Return All is off. Useful while you are still testing the workflow.

Renaming happens more often than anyone plans for, usually after two squads merge. This operation edits an existing team, and both fields it can change sit in the optional Update Fields collection.

• Organization Slug Name or ID: the slug of the organization the team belongs to.
• Team Slug Name or ID: the slug of the team to update, picked from the list or passed as {{ $json.field }}.
• Name: the new name of the team.
• Slug: the new slug. It has to be unique and available, so a collision is worth handling on the error branch.