Resources · Make integration

Sentry Make integrationAutomate Sentry with Make.

Can Make take the Sentry busywork off your plate? The Sentry Make integration gives you 27 modules, one instant trigger among them. This page shows developers and ops leads how to connect a token and build a first scenario that works.

Try the Sentry integration on Make See the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sentry Make integration automate?

The Sentry Make integration links your Sentry account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick that triggers, acts or searches. With 27 modules, including one instant trigger, Make can react to Sentry events and manage projects, teams and issues for you.

Alerts your developers actually read. Watch Events starts a scenario when Sentry reports an event. Get an Issue then adds the title, the first and last seen dates and the user reports, and the message lands in the chat your team already watches.

Projects that set themselves up. When a new client app is approved in your CRM or a form, Create a Team and Create a Project build its Sentry home in one pass, named the same way every time.

An access review without the spreadsheet chore. List an Organization's Users and List an Organization's Teams export who belongs where, so an ops lead can spot accounts that should be closed.

What Make does not offer here: there is no scheduled trigger and no module to add or remove members, and the Make documentation for Sentry is flagged as AI-generated, to be checked against Sentry's own docs. Make an API Call covers the endpoints the list skips. The same app often has an n8n node, and the n8n vs Make comparison lays out how the two tools differ. To go further, the Make training teaches the editor step by step, and the Make pricing guide explains how operations are counted.

Connect

How do you connect Sentry to Make?

01
Add a Sentry module
In your scenario, add any Sentry module and click Create a connection. A connection is your Sentry account linked to Make once, then reused by every Sentry module. For Watch Events, click Create a webhook first, then Create a connection.
02
Create an API token in Sentry
In Sentry, open User Settings, then API Tokens, and click Create New Token. Tick the scopes your modules need, click Create Token and copy the token displayed on screen.
03
Paste the token and name the connection
Back in Make, you can type a label in Connection name, such as the organization it points to. Paste the token and save. Make can now list your Sentry projects and teams inside the module fields.

First scenario

Your first scenario: a Sentry team and project for every new app

GoalWhen a new app is approved in the tool where your team logs requests, Make creates its team and its project in Sentry.

01
Create the scenario
From the Scenarios page, create a new scenario and click the +. The first module is the trigger of the app where requests get approved, a form or a table for instance.
02
Add Create a Team
Click the + on the right of that first module, search Sentry and pick Create a Team. Choose your connection, then your organization from the list Make shows, and map the app name from the request.
03
Chain Create a Project
Add Create a Project right after it. Map the team produced by the previous module so the project is bound to it, and reuse the app name for the project name.
04
Test with Run once
Click Run once and send a test request. Each module shows the bundle it received; check that the team and the project now appear in Sentry, then remove the test entries.
05
Schedule and switch it on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on, and each approved request turns into a ready Sentry project.

Triggers

What can start a Sentry scenario?

1 module starts a scenario when something happens in Sentry. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Sentry as soon as it happens.

Sentry1Watch Events

Watch Events

Instant trigger

In Make“Watches events.”

Watch Events opens your scenario the moment Sentry reports a new event, so an error your users hit can reach your team without anyone refreshing a dashboard. Each event arrives as one bundle, the item passed on to the next module.

How it fires

instant: Sentry calls Make through a webhook as soon as it happens. When you add the module, click Create a webhook, then Create a connection.

When to use it

any flow that should react to fresh events, such as pulling the related issue with Get an Issue and posting it where your developers work.

Watch out

every event starts a run, and each module that processes it counts as one operation on your plan.

Modules

What can Make do in Sentry?

Sentry gives you 26 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Sentry1

Create a Project

Action

In Make“Creates a new project bound to a team.”

Create a Project adds a new Sentry project under a team you pick, ready to receive events from a fresh app or service.

When to use it

when a new product or client site enters your pipeline and you want its Sentry project set up the same way every time, straight from the tool where the request was logged.

Watch out

the project must belong to a team, so create or find that team first; Create a Team or List an Organization's Teams gives you one.

Sentry2

Create a Team

Action

In Make“Creates a new team bound to an organization.”

With Create a Team, a new team appears inside your Sentry organization, ready to own the projects you attach to it.

When to use it

when a new squad forms, so the team exists in Sentry before anyone asks for access, and a following Create a Project can attach to it directly.

Watch out

a team always sits inside an organization; if your token reaches several, List Organizations helps you pick the right one.

Sentry3

Delete an Issue

Action

In Make“Removes an individual issue.”

Delete an Issue removes one issue from Sentry, which keeps a project clear of noise you already know is harmless.

When to use it

once you have identified an issue as a test or a duplicate, typically found with List a Project's Issues earlier in the scenario.

Watch out

Make has no module to bring a deleted issue back; try the scenario with Run once on a test project before you let it touch real issues.

Sentry4

Delete a Project

Action

In Make“Schedules a project for deletion. Deletion happens asynchronously and therefore is not immediate. However, once deletion has begun the state of a project changes and will be hidden from most public views. Requires the following scopes: "project:admin".”

Delete a Project hands Sentry a request to remove a whole project, the tidy way to retire an app nobody maintains anymore.

When to use it

at the end of a decommission flow, once the data you want to keep has been copied elsewhere.

Watch out

Sentry schedules the deletion and runs it asynchronously, so it is not immediate, yet the project disappears from most public views as soon as it starts. Your token also needs the project:admin scope.

Sentry5

Delete a Team

Action

In Make“Schedules a team for deletion. Note: Deletion happens asynchronously and therefore is not immediate. However once deletion has begun the state of a project changes and will be hidden from most public views.”

This module queues a Sentry team for removal and cleans up your organization after a reorganization.

When to use it

when a team has been merged into another and its projects have moved, something List a Team's Projects lets you confirm beforehand.

Watch out

as with projects, the removal is asynchronous and not immediate; once it begins, the team drops out of most public views, so do not expect it to vanish in the same second.

Sentry6

Get an Event

Action

In Make“Returns details on an individual event.”

Get an Event fetches the full details of a single Sentry event, one occurrence rather than the grouped issue.

When to use it

after Watch Events or List an Issue's Events, when the next module needs more than what arrived, for example to write a detailed message for the developer on call.

Watch out

it reads one event per call and each call is one operation, so avoid running it on every bundle of a long list without a reason.

Sentry7

Get an Issue

Action

In Make“Returns details on an individual issue. This returns the basic stats for the issue (title, last seen, first seen), some overall numbers (number of comments, user reports) as well as the summarized event data.”

Get an Issue returns the summary of one issue: its title, when it was first and last seen, counts such as comments and user reports, plus summarized event data.

When to use it

to turn a raw alert into a readable card, with enough context for a product manager to judge the impact.

Watch out

the module needs the issue to read, which an earlier module such as List a Project's Issues can supply.

Sentry8

Get an Organization

Action

In Make“Returns details on an individual organization including various details such as membership access, features, and teams.”

Point Get an Organization at your Sentry organization and it brings back its details, including membership access, features and teams.

When to use it

in an audit flow that writes the state of your organization to a sheet or a document, so leadership sees who can access what without logging into Sentry.

Watch out

the result is a single bundle holding many details; map only the values you need into the next module to keep it readable.

Sentry9

Get a Project

Action

In Make“Returns details on an individual project.”

Get a Project looks up one Sentry project and returns its details, handy when a later module needs to know what is there.

When to use it

before Update a Project, to read the current state and decide whether a change is needed, or to enrich a report built from List Projects.

Watch out

it targets one project only; to cover all of them, start with List Projects, which returns one bundle per project.

Sentry10

Get a Team

Action

In Make“Returns details on an individual team.”

Get a Team gives you the details of a single team, a quick way to pull its information into a message or a report.

When to use it

in a flow that routes each new issue to a team, after you have found that team with List an Organization's Teams.

Watch out

it returns the team itself, not its projects; for those, List a Team's Projects is the module to add.

Sentry11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Sentry API from your scenario, using the same connection as the other modules.

When to use it

when none of the listed modules does what you need; you keep your token and skip building authentication by hand.

Watch out

you write the request yourself, so keep the Sentry API reference open and make sure the scopes of your token cover the endpoint you call.

Sentry12

Update an Issue

Action

In Make“Updates an individual issue's attributes.”

Update an Issue changes the attributes of one issue in Sentry, so the state of a bug can follow what happens in your other tools.

When to use it

when a ticket is closed in your project tracker and you want the matching Sentry issue updated too, without a developer switching tabs.

Watch out

Make needs the exact issue to change; find it first with List a Project's Issues, then map it into this module.

Sentry13

Update an Organization

Action

In Make“Updates various attributes and configurable settings for the given organization.”

Update an Organization edits the attributes and configurable settings of your Sentry organization from inside a scenario.

When to use it

rarely, and on purpose: when a change approved elsewhere, in a request form for instance, should reach the organization without someone opening its settings page.

Watch out

the change applies to the whole organization; test with Run once and read the bundle before you switch the scenario on.

Sentry14

Update a Project

Action

In Make“Updates various attributes and configurable settings for the given project. Only supplied values are updated. Requires "project:write" scope.”

Update a Project adjusts a project's attributes and settings, and only the values you fill in change; everything else stays as it was.

When to use it

to keep projects aligned when a service is renamed or changes hands, with the new values coming from the tool where the change was recorded.

Watch out

Sentry requires the project:write scope on your token for this module, so check it when you create the token.

Sentry15

Update a Team

Action

In Make“Updates various attributes and configurable settings for the given team.”

When a team changes, Update a Team brings its attributes and settings in Sentry up to date without leaving the scenario.

When to use it

after a reorganization recorded in your HR or project tool, so team details in Sentry match the rest of your stack.

Watch out

you point the module at one team; adding Get a Team first lets you compare the current state with the change you are about to send.

Sentry16

List an Issue's Events

In Make“Returns an issue's events.”

List an Issue's Events gathers the events behind one issue, each returned as its own bundle, so you can see how the same error shows up across occurrences.

When to use it

during an investigation, sending the events of a noisy issue to a sheet where the team can sort and compare them.

Watch out

a busy issue can return many bundles, and every module after it runs once per bundle, which adds operations quickly.

Sentry17

List an Organization's Repositories

In Make“Returns a list of version control repositories for a given organization.”

This search returns the version control repositories that Sentry holds for a given organization.

When to use it

for an inventory of the code repositories Sentry knows about, written to a table your engineering lead can review at a glance.

Watch out

like any search, it can return zero, one or several bundles, so plan for the empty case when you map its output into the next module.

Sentry18

List an Organization's Teams

In Make“Returns a list of teams bound to an organization.”

List an Organization's Teams brings back the teams bound to an organization, one bundle per team.

When to use it

as the first step of any flow that works team by team, for example one that then fetches each team's projects with List a Team's Projects.

Watch out

the modules that follow run once per team returned, so the operation count grows with the size of your organization.

Sentry19

List an Organization's Users

In Make“Returns a list of users that belong to a given organization.”

Get the list of users who belong to an organization with this search, each user arriving as a separate bundle.

When to use it

for an access review, comparing Sentry members with your HR list so that someone who has left the company does not keep access.

Watch out

the module only lists users; it removes nobody, so the cleanup itself still happens in Sentry.

Sentry20

List a Project's Events

In Make“Returns a list of events bound to a project.”

List a Project's Events returns the events bound to one project, across all its issues rather than a single one.

When to use it

when you want a wider view than one issue, for instance to export a project's events to a spreadsheet for a post-release review.

Watch out

on an active project the list can be long, and every bundle it returns costs an operation in each module that follows.

Sentry21

List a Project's Issues

In Make“Returns a list of issues (groups) bound to a project.”

List a Project's Issues pulls the issues, which Sentry also calls groups, attached to a project, one bundle each.

When to use it

as the starting point of a triage flow: list the issues, then use Get an Issue or Update an Issue on the ones that matter.

Watch out

chaining it with Delete an Issue is risky; check each bundle with Run once before letting deletions run on the whole list.

Sentry22

List a Project's Users

In Make“Returns a list of users seen within the specified project.”

List a Project's Users returns the users Sentry has seen within a given project, one bundle per user.

When to use it

to send the users seen on a project to your support tool, so the support team knows whom to contact after a faulty release.

Watch out

this is not the same list as List an Organization's Users, which covers the members of your organization; pick the one that answers your question.

Sentry23

List a Tag's Values

In Make“Returns a list of values associated with this key. The query parameter can be used to perform a "contains" match on values.”

List a Tag's Values returns the values recorded for one tag key, and its query parameter narrows the result to values containing a piece of text.

When to use it

to find which values actually appear under a tag before you build a report around them.

Watch out

the filter is a “contains” match, not an exact one, so a short query can return more values than you expect.

Sentry24

List a Team's Projects

In Make“Returns a list of projects bound to a team.”

List a Team's Projects returns the projects bound to a given team, one bundle per project.

When to use it

before deleting or merging a team, to see what it still owns, or to send each team a summary of its own projects.

Watch out

you need the team first; List an Organization's Teams or Get a Team gives you the value to map into it.

Sentry25

List Organizations

In Make“Returns a list of organizations available to the authenticated session.”

List Organizations shows the organizations available to your connection, based on the token you gave Make.

When to use it

for agencies or groups that manage several Sentry organizations and want one scenario that goes through each of them.

Watch out

the list only covers what the authenticated session can see, so the token you created decides what shows up.

Sentry26

List Projects

In Make“Returns a list of projects available to the authenticated session.”

Need a full inventory? List Projects returns every project available to your connection, one bundle each.

When to use it

to build a catalog of your Sentry projects, then enrich each line with Get a Project before writing it to a sheet.

Watch out

unlike List a Team's Projects, it is not filtered by team; use that module instead when you only need one team's scope.

Need help

Need help automating Sentry with Make?

A person reads every message.

FAQ

Sentry and Make: frequently asked questions

01Is the Sentry Make integration free?

Yes. Sentry is a standard app, so its modules work on the Make Free plan. That plan gives you 2 active scenarios, 15 minutes minimum between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. Your Sentry subscription is separate and follows Sentry's own pricing page.

02What do you need to connect Sentry to Make?

An active Sentry account and an API token with the right scopes. You create the token in Sentry under User Settings, API Tokens, Create New Token, choosing the scopes before clicking Create Token. In Make, add a Sentry module, click Create a connection, name it if you like and paste the token. For the Watch Events trigger, Make asks you to click Create a webhook before the connection. Some modules need specific scopes, such as project:admin for Delete a Project.

03Does the Sentry Watch Events trigger work in real time?

Yes. Watch Events is an instant trigger: Sentry calls Make through a webhook as soon as an event happens, instead of Make checking on a schedule. The scenario therefore starts on the event itself, and the default schedule of new scenarios does not apply to it. Each event is one bundle, and every module that processes it uses one operation. Sentry has no scheduled trigger in Make, so polling is not an option this app offers.

04What if a Sentry module is missing in Make?

Use Make an API Call. It reaches any endpoint of the Sentry API with the connection you already have, so you are not limited to the 15 actions and 11 searches listed in Make. Check that your token carries the scopes the endpoint needs. Keep in mind that the Make documentation for Sentry is marked as AI-generated from the official Sentry docs, so confirm important details, such as required scopes, in Sentry's own documentation before relying on them.

05Make or n8n for Sentry?

It depends on what you compare. On Make, Sentry comes with 27 modules, an instant Watch Events trigger and Make an API Call for everything else, all set up in a visual scenario. The same app often has an n8n node too. The fair test is to write down the actions your flow needs, check which tool covers each one natively, and pick the one that handles your list with the fewest workarounds. The comparison page linked in the section above goes into the details.

Add a Sentry module

Create an API token in Sentry

Paste the token and name the connection

Create the scenario

Add Create a Team

Chain Create a Project

Test with Run once

Schedule and switch it on

Need help automating Sentry with Make?