Sentry

Connect Sentry to Sharick and error alerts land directly in your inbox: new issues arrive as inbox items, regressions (an issue you fixed that came back) are flagged critical, and recoveries are recorded quietly without interrupting you.

A connection can be shared with teammates — everyone invited to it receives the same alerts.

Prerequisites

• The Sharick desktop app, logged in.
• A Sentry account with permission to create internal integrations in your organization (usually Owner or Manager role).

Step 1 — Create a connection in Sharick

1. Open the Sharick desktop app and go to Settings → Integrations → Sentry.
2. Click Add connection, give it a name that tells you which project it watches (e.g. myapp-prod), and click Create.
3. The new connection card shows a Webhook URL with a copy button. Copy it — you’ll paste it into Sentry in the next step.

The card shows Waiting for client secret for now. That’s expected — you’ll get the secret from Sentry in Step 2.

Note

The webhook URL is the same for all of your connections. Sharick tells connections apart by their client secret, so create one Sharick connection per Sentry integration.

Step 2 — Create an internal integration in Sentry

1. In Sentry, go to Settings → Developer Settings → Custom Integrations and click Create New Integration.
2. Choose Internal Integration and name it (e.g. Sharick).
3. In Webhook URL, paste the URL you copied from Sharick.
4. Under Permissions, grant Issue & Event: Read.
5. Under Webhooks, enable the issue resource. This is what makes Sentry send created / regressed / resolved issue events to Sharick.
6. Save the integration.
7. Sentry now shows a Client Secret for the integration. Copy it.

Sentry’s settings layout moves around between versions — if the menus look different, the essentials are unchanged: an internal integration with your Sharick webhook URL, issue webhooks enabled, and its client secret copied.

Step 3 — Paste the client secret into Sharick

1. Back in Settings → Integrations → Sentry, find your connection card and paste the secret into the Sentry client secret field, then click Save.
2. The badge flips from Waiting for client secret to Connected.

The secret is write-only: Sharick uses it to verify Sentry’s webhook signatures and never displays it again (only the last few characters, so you can tell secrets apart). To swap in a new one later, use Replace.

Verify it worked

Trigger a test error in the project the integration covers — throw an exception in a dev branch, or use sentry-cli send-event — so Sentry creates a new issue (an event on an existing issue won’t trigger anything).

Within about a minute, the issue should appear as an item in your Sharick inbox, linking back to the Sentry issue. If it did: you’re done.

Share the connection with teammates

Alerts often matter to more than one person. On the connection card, under Alert recipients:

1. Enter a teammate’s email and click Invite.
2. They’ll see the invitation in their own Settings → Integrations → Sentry and can accept or decline.
3. Once accepted, they receive the same alerts you do. Owners can remove members or revoke pending invitations at any time.

Members can leave a connection whenever they want; only the owner can disconnect it for everyone.

Troubleshooting

The card still says “Waiting for client secret”

The secret was never saved. Paste it and click Save — if saving fails, the card shows the error inline.

Connected, but no alerts arrive

Work through these in order — each one has caught real setups:

1. Wrong webhook URL. In Sentry, open your integration and confirm the Webhook URL exactly matches the one on your Sharick connection card.
2. Issue webhooks not enabled. In the Sentry integration settings, confirm the issue resource is checked under Webhooks. Without it, Sentry never sends anything.
3. Wrong client secret. If the secret in Sharick doesn’t match the integration that’s sending, Sharick rejects the delivery as unsigned. Copy the client secret from the Sentry integration again and use Replace on the connection card.
4. Sentry isn’t sending. In Sentry’s integration page, check the request log / webhook deliveries. If deliveries show errors there, the response code tells you which side failed.
5. No new issue was created. Repeated events on an already-open issue don’t create alerts. Resolve the issue in Sentry first, then trigger the error again — that’s a regression, and it will arrive flagged critical.

Alerts arrive twice

Two connections are probably configured with secrets from the same Sentry integration, or two Sentry integrations point at Sharick for the same project. Keep the pairing one-to-one and disconnect the extra.