Skip to main content

​
Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Render connector page.

​
How Render webhooks are set up

StackOne creates and manages the webhook subscription automatically when the account is connected — there is nothing to configure in Render and no URL to paste. StackOne registers one Render webhook named StackOne, subscribed to the events you enable, and deletes it when the account is disconnected.

  • No callback URL to copy, and no verification step to complete.
  • Set Webhook Workspace ID (tea-…) when your API key belongs to more than one workspace; otherwise the first workspace is used.
  • Pro workspaces allow one webhook destination. If one already exists, delete it or upgrade to Scale before connecting.

​
Available webhook events

The following Render events can be enabled. Only events selected in StackOne are added to the webhook’s event filter and delivered.

1

Deploys events

Build, deploy, job and cron job lifecycle events for services. build_ended, deploy_ended, job_run_ended and cron_job_run_ended carry data.status (succeeded, failed or canceled).

  • Artifact Fetch Failed (artifact_fetch_failed) — Fired when a build artifact published by the service’s build source could not be fetched
  • Artifact Source Changed (artifact_source_changed) — Fired when the build source linked to the service is attached, detached or replaced
  • Branch Deleted (branch_deleted) — Fired when the Git branch the service deploys from is deleted
  • Build Started (build_started) — Fired when a build starts for the service
  • Build Ended (build_ended) — Fired when a build finishes for the service
  • Commit Ignored (commit_ignored) — Fired when a pushed commit is skipped (for example by a skip-deploy marker or build filter) and no deploy starts
  • Pre-Deploy Started (pre_deploy_started) — Fired when the service’s pre-deploy command starts
  • Pre-Deploy Ended (pre_deploy_ended) — Fired when the service’s pre-deploy command finishes
  • Deploy Started (deploy_started) — Fired when a deploy starts for the service
  • Deploy Ended (deploy_ended) — Fired when a deploy finishes for the service
  • Image Pull Failed (image_pull_failed) — Fired when Render cannot pull the container image for an image-backed service
  • Job Run Ended (job_run_ended) — Fired when a one-off job created for the service finishes
  • Cron Job Run Started (cron_job_run_started) — Fired when a cron job run starts
  • Cron Job Run Ended (cron_job_run_ended) — Fired when a cron job run finishes
  • Pipeline Minutes Exhausted (pipeline_minutes_exhausted) — Fired when the workspace runs out of included pipeline (build) minutes
2

Service Availability events

Instance health, suspension, maintenance, and zero-downtime redeploy events for services.

  • Server Available (server_available) — Fired when a service instance becomes available and starts receiving traffic
  • Server Failed (server_failed) — Fired when a service instance fails (for example a crash or failed health check)
  • Server Hardware Failure (server_hardware_failure) — Fired when a service instance is affected by an underlying hardware failure
  • Server Restarted (server_restarted) — Fired when a service instance restarts
  • Service Suspended (service_suspended) — Fired when the service is suspended
  • Service Resumed (service_resumed) — Fired when a suspended service is resumed
  • Maintenance Started (maintenance_started) — Fired when Render starts a maintenance window on the service
  • Maintenance Ended (maintenance_ended) — Fired when a maintenance window on the service ends
  • Maintenance Mode Enabled (maintenance_mode_enabled) — Fired when maintenance mode is turned on or off for the service
  • Maintenance Mode URI Updated (maintenance_mode_uri_updated) — Fired when the maintenance page URI of the service changes
  • Zero-Downtime Redeploy Started (zero_downtime_redeploy_started) — Fired when Render starts a zero-downtime redeploy of the service
  • Zero-Downtime Redeploy Ended (zero_downtime_redeploy_ended) — Fired when a zero-downtime redeploy of the service finishes
3

Scaling events

Instance count, autoscaling and plan changes for services.

  • Instance Count Changed (instance_count_changed) — Fired when the number of instances of the service changes (manual scale or autoscaling)
  • Autoscaling Config Changed (autoscaling_config_changed) — Fired when the service’s autoscaling settings (enabled, min, max, CPU and memory targets) change
  • Autoscaling Started (autoscaling_started) — Fired when autoscaling begins changing the service’s instance count
  • Autoscaling Ended (autoscaling_ended) — Fired when an autoscaling operation on the service finishes
  • Plan Changed (plan_changed) — Fired when the service’s instance type (plan) changes
4

Postgres events

Lifecycle, backup, high-availability, upgrade, restore and recovery events for Render Postgres databases.

  • Postgres Created (postgres_created) — Fired when a Render Postgres database is created
  • Postgres Available (postgres_available) — Fired when a Postgres database becomes available
  • Postgres Unavailable (postgres_unavailable) — Fired when a Postgres database becomes unavailable
  • Postgres Restarted (postgres_restarted) — Fired when a Postgres database restarts
  • Postgres Backup Started (postgres_backup_started) — Fired when a Postgres backup (export) starts
  • Postgres Backup Completed (postgres_backup_completed) — Fired when a Postgres backup (export) completes
  • Postgres Backup Failed (postgres_backup_failed) — Fired when a Postgres backup (export) fails
  • Postgres Cluster Leader Changed (postgres_cluster_leader_changed) — Fired when the primary of a high-availability Postgres cluster fails over to another node
  • Postgres Connection Pool Toggled (postgres_connection_pool_enabled_changed) — Fired when connection pooling is turned on or off for a Postgres database
  • Postgres Connection Pool Changed (postgres_connection_pool_changed) — Fired when the connection pool settings of a Postgres database change
  • Postgres Disk Size Changed (postgres_disk_size_changed) — Fired when the disk size of a Postgres database changes
  • Postgres Disk Autoscaling Toggled (postgres_disk_autoscaling_enabled_changed) — Fired when disk autoscaling is turned on or off for a Postgres database
  • Postgres HA Status Changed (postgres_ha_status_changed) — Fired when the high-availability status of a Postgres database changes
  • Postgres Upgrade Started (postgres_upgrade_started) — Fired when a Postgres major-version upgrade starts
  • Postgres Upgrade Succeeded (postgres_upgrade_succeeded) — Fired when a Postgres major-version upgrade succeeds
  • Postgres Upgrade Failed (postgres_upgrade_failed) — Fired when a Postgres major-version upgrade fails
  • Postgres Restore Succeeded (postgres_restore_succeeded) — Fired when a point-in-time restore of a Postgres database succeeds
  • Postgres Restore Failed (postgres_restore_failed) — Fired when a point-in-time restore of a Postgres database fails
  • Postgres Read Replicas Changed (postgres_read_replicas_changed) — Fired when read replicas are added to or removed from a Postgres database
  • Postgres Read Replica Stale (postgres_read_replica_stale) — Fired when a Postgres read replica falls too far behind its primary
  • Postgres PITR Checkpoint Started (postgres_pitr_checkpoint_started) — Fired when a point-in-time-recovery checkpoint starts
  • Postgres PITR Checkpoint Completed (postgres_pitr_checkpoint_completed) — Fired when a point-in-time-recovery checkpoint completes
  • Postgres PITR Checkpoint Failed (postgres_pitr_checkpoint_failed) — Fired when a point-in-time-recovery checkpoint fails
  • Postgres WAL Archive Failed (postgres_wal_archive_failed) — Fired when archiving of Postgres write-ahead logs fails
5

Key Value and Disks events

Render Key Value instance health and persistent disk changes.

  • Key Value Available (key_value_available) — Fired when a Render Key Value instance becomes available
  • Key Value Unhealthy (key_value_unhealthy) — Fired when a Render Key Value instance becomes unhealthy
  • Key Value Config Restart (key_value_config_restart) — Fired when a Render Key Value instance restarts to apply a configuration change
  • Disk Created (disk_created) — Fired when a persistent disk is attached to the service
  • Disk Updated (disk_updated) — Fired when a persistent disk on the service is updated (for example resized)
  • Disk Deleted (disk_deleted) — Fired when a persistent disk is removed from the service

​
Delivery format

Render sends one event per request. The body is a thin envelope, and StackOne emits it unchanged as the event data.

  • Body: type, timestamp and data with id (evt-…), serviceId, serviceName and, on ended events, status.
  • The emitted event ID is the Render event ID (data.id, evt-). Fetch it with the retrieve_event action for the event-specific details; data.serviceId identifies the affected resource.
  • Render retries failed deliveries up to 8 times over about 33 hours and disables the webhook if every attempt fails.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.