• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Manage files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

Email and Slack Notifications

Receive updates about important Render service events.

Render can notify you via email and/or Slack when certain events occur (such as when your service's deploy fails). You can set workspace-level defaults for notifications, and you can also customize notifications for individual services.

Want to trigger custom workflows from a wide variety of platform events?

See Webhooks.

Supported notifications

Render can notify you of the following events, depending on which notification level you set (Only failure notifications or All notifications):

EventMinimum Notification LevelSupports EmailSupports Slack

A service build or deploy fails.

Only failure notifications

🟢🟢

A Docker image pull fails.

Only failure notifications

🟢🟢

A cron job execution fails.

Only failure notifications

🟢🟢

A running service becomes unhealthy.

Only failure notifications

🟢🟢

A service's persistent disk usage exceeds 80% of the disk's allocated space.

Only failure notifications

🟢🟢

A Blueprint sync fails.

Only failure notifications

🟢🟢

Render suspends a service that repeatedly fails to start and become healthy over a 24-hour period.

This is often caused by a service configuration error, a bug in application code, or an undersized compute plan for your resource requirements.

Only failure notifications

🟢🟢

A one-off job's execution fails.

Only failure notifications

❌🟢

A deploy successfully goes live.

All notifications

❌🟢

An unhealthy service becomes healthy.

All notifications

❌🟢

A service's persistent disk usage drops back below 80% of the disk's allocated space.

All notifications

🟢🟢

To request notification support for additional events, please submit a feature request.

Setting workspace defaults

From your workspace home in the Render Dashboard, click Integrations > Notifications in the left pane:

Notifications settings in the Render Dashboard

From here, you can configure the following:

SettingDescription

Notification Destination

Receive notifications via Email, Slack, or both.

To receive via Slack, you must first connect your Slack workspace.

Default Service Notifications

Specifies which supported notifications Render sends for your services. Options include:

  • Only failure notifications. Render sends notifications only for failures (includes failed deploys, cron jobs, and running services).
  • All notifications. Render sends all supported notifications, including for successful deploys.
  • None. Render does not send any notifications.

Preview Notifications

If Enabled, Render sends the same set of notifications for a service preview or preview environment that it does for the preview's base service.

This setting requires a Pro workspace or higher.

Connecting to Slack

From your workspace's Integrations > Notifications page, click Connect Slack under the Notification Destination setting:

Connecting Slack in the Render Dashboard

Proceed through the authorization flow to connect your Slack account.

Customizing per service

You can customize notification settings for an individual service. Doing so overrides your workspace's default notification settings for that service.

In the Render Dashboard, go to your service's Settings page and scroll down to Notifications:

Overriding notification settings for an individual service in the Render Dashboard

For any setting, choose a value besides Use workspace default to customize the service's notification behavior.

After you customize notification settings for a service, that service appears in your workspace's Integrations > Notifications page, under Notification Overrides:

List of services that override notification settings in the Render Dashboard

Email and Slack Notifications
  • Supported notifications
  • Setting workspace defaults
    • Connecting to Slack
  • Customizing per service
All Systems Operational
© Render Inc. All rights reserved.