Notifications

Stay informed about code reviews, billing, and team activity with customizable notifications.

Notification Channels

Jasper supports multiple notification channels to fit your workflow:

Email

Traditional email notifications. Enabled by default for all events.

Slack

Get notifications in your Slack channels via incoming webhooks.

Discord

Send notifications to Discord channels via webhooks.

Microsoft Teams

Integrate with Teams via incoming webhooks.

In-App Notifications

Receive notifications directly in the Jasper dashboard. Always enabled for critical alerts.

Notification Types

Configure notifications for different event categories:

Review Notifications

Event Description Default
Review Completed Notified when a code review finishes successfully Email, In-App
Review Failed Alerted when a review encounters an error Email, In-App
Comments Posted Notified when Jasper posts inline comments In-App only

Billing Notifications

Event Description Default
Low Credits Warning Alert when credits drop below threshold Email, In-App
Purchase Confirmation Receipt after buying credits Email
Monthly Summary Monthly usage and billing summary Email

Team Notifications

Event Description Default
Member Joined Notified when someone joins your organization Email, In-App
Role Changed Alerted when a member's role is updated In-App
Member Removed Notified when someone leaves or is removed In-App

Configuring Preferences

Customize your notification preferences:

  1. Click your profile icon and select Personal Settings
  2. Navigate to the Notifications tab
  3. Toggle channels on/off for each notification type
  4. Click Save Preferences

Tip

Use different channels for different events. For example, send low-credit warnings to Slack for immediate visibility, but keep purchase receipts in email for records.

Setting Up Integrations

Slack Integration

  1. In Slack, go to your workspace settings
  2. Navigate to Apps → Manage → Custom Integrations
  3. Create an Incoming Webhook
  4. Choose the channel for notifications
  5. Copy the webhook URL
  6. In Jasper, go to Personal Settings → Integrations
  7. Paste the webhook URL in the Slack field
  8. Click Test to verify the connection
  9. Enable desired notification types

Discord Integration

  1. In Discord, right-click on the channel
  2. Select Edit Channel → Integrations → Webhooks
  3. Create a new webhook and copy the URL
  4. In Jasper, paste the URL in Personal Settings
  5. Test and enable the integration

Microsoft Teams Integration

  1. In Teams, go to the channel settings
  2. Select Connectors → Incoming Webhook
  3. Configure and copy the webhook URL
  4. Add the URL in Jasper settings
  5. Test the connection

Testing Notifications

Each integration has a Test button that sends a sample notification. Use this to verify your webhook URLs are correct and notifications appear as expected.

Notification Email Address

By default, email notifications are sent to your GitHub-associated email. You can set a different notification email in Personal Settings → Profile.

Organization-Wide Notifications

Organization owners can configure organization-level notification webhooks in Settings → Organization → Webhooks. These are separate from personal notification preferences and useful for:

  • Sending all review events to a team channel
  • Integrating with external monitoring systems
  • Creating automated workflows

See Webhooks documentation for more details.

Troubleshooting

Not receiving email notifications?

  • Check your spam/junk folder
  • Verify your notification email address in Personal Settings
  • Ensure the notification type is enabled for email

Slack/Discord/Teams not working?

  • Use the Test button to verify the webhook URL
  • Ensure the webhook hasn't been deleted or regenerated
  • Check that the integration is enabled (toggle is on)
  • Verify channel permissions allow the webhook to post

Too many notifications?

  • Disable channels you don't actively monitor
  • Turn off less critical notification types
  • Consider using in-app only for low-priority events