Render

Connect Cased to Render to deploy services, monitor infrastructure, and manage your cloud applications

Render

Render is a unified cloud platform to build and run all your apps and websites with free TLS certificates, global CDN, private networks and auto deploys from Git. Cased integrates with Render to help you manage deployments, monitor services, and track your cloud infrastructure.

Available Actions

With Render connected, Cased agents can handle:

• Service Management: List and monitor web services, background workers, cron jobs, and static sites
• Service Control: Suspend, resume, and restart services
• Database Operations: Manage PostgreSQL and Redis instances with connection information
• Deployment Control: Trigger deployments, cancel in-progress deploys, list deployment history
• Metrics & Monitoring: Access detailed CPU, memory, HTTP latency, bandwidth, and disk metrics
• Environment Management: Work with environment groups for shared configurations
• Domain Management: List and manage custom domains across services

Setup

To connect Render to Cased:

1. Visit https://dashboard.render.com/u/settings
2. Navigate to the API Keys section
3. Create a new API key with appropriate permissions for your organization

Connect to Cased

1. Go to app.cased.com/connections/render
2. Enter your Render API key
3. Cased agent will start using the Render connection

Workflow Triggers

Cased can automatically trigger workflows when Render events occur. This enables automated responses for:

• Deployment failures and build errors
• Service outages and health issues
• Auto-scaling events
• Service suspension and resumption

Setting Up Webhook Triggers

1. Get your Cased webhook URL:

   • Go to app.cased.com/connections/render
   • After connecting, your webhook URL will be displayed
   • The URL format is: https://app.cased.com/webhooks/<webhook_token>/render/

2. Configure Render to send webhooks:

   • In Render Dashboard, go to Account Settings → Integrations → Webhooks
   • Click “Add Webhook”
   • Enter a name (e.g., Cased)
   • Paste your webhook URL from Cased
   • Select the events you want to trigger workflows (see supported events below)
   • Click Save

3. Create a workflow in Cased:

   • Go to app.cased.com/agents
   • Click “Create Agent”
   • Under triggers, select “Render” and choose the events to respond to
   • Configure your workflow instructions

Supported Events

Category	Events
Deploy	deploy:started, deploy:ended, build:started, build:ended
Service Health	server:failed, server:available, service:suspended, service:resumed
Scaling	autoscaling:started, autoscaling:ended, instance:scaled

Event Context

When a Render event triggers a workflow, Cased provides the following context variables:

Variable	Description
event_type	The type of event (e.g., deploy_ended, server_failed)
service_id	The Render service ID
service_name	The service name
status	Event status (e.g., succeeded, failed, canceled)
deploy_id	Deployment ID (for deploy events)
commit_id	Git commit ID (for deploy events)
commit_message	Git commit message (for deploy events)
instance_count	Current instance count (for scaling events)
previous_instance_count	Previous instance count (for scaling events)
timestamp	When the event occurred

Metrics

Cased can query detailed metrics from your Render services:

Metric Type	Description
cpu	CPU usage percentage
memory	Memory usage in bytes
http_requests	Request count by status code
http_latency	Response time percentiles (p50, p95, p99)
bandwidth	Network bandwidth usage
disk_usage	Disk space used (databases)
disk_capacity	Total disk capacity (databases)
active_connections	Database connection count
replication_lag	Replica lag in seconds (databases)
instance_count	Number of running instances

Example Workflows

Deploy Failure Analysis

Create a workflow that automatically investigates failed deployments:

When a deploy fails on Render:
1. Get the deployment logs
2. Analyze the build output for errors
3. Check recent commits for potential issues
4. Post findings to Slack with remediation suggestions

Auto-Scaling Monitor

Monitor scaling events and ensure services scale appropriately:

When auto-scaling occurs on Render:
1. Check current CPU and memory metrics
2. Compare against historical patterns
3. Alert if scaling seems unusual
4. Log scaling event for capacity planning

Service Health Response

Respond to service outages automatically:

When a server fails on Render:
1. Check service logs for errors
2. Verify database connectivity
3. Check recent deployments
4. Attempt service restart if appropriate
5. Notify on-call team via Slack