Integrations · Playbook

What an AI coworker
can do in Render.

The Render integration exposes 24 actions — 20 read,4 write — that any agent, team or AI employee can use once Render is connected at the organization level. Every write can be gated behindhuman approval, and every call lands in theaudit trail.

Read actions (20)

Safe to run freely — they observe, fetch and search.

ActionFunctionKey params

Create cron jobcreate_cron_jobname, schedule, runtime, buildCommand, startCommand

Create key valuecreate_key_valuename

Create static sitecreate_static_sitename, buildCommand

Create web servicecreate_web_servicename, runtime, buildCommand, startCommand

Get deployget_deployserviceId, deployId

Get key valueget_key_valuekeyValueId

Get metricsget_metricsresourceId, metricTypes

Get selected workspaceget_selected_workspace—

Get serviceget_serviceserviceId

List deployslist_deploysserviceId

List key valuelist_key_value—

List log label valueslist_log_label_valueslabel, resource

List logslist_logsresource

List serviceslist_services—

List workspaceslist_workspaces—

Select workspaceselect_workspaceownerID

Update cron jobupdate_cron_jobserviceId

Update environment variablesupdate_environment_variablesserviceId, envVars

Update static siteupdate_static_siteserviceId

Update web serviceupdate_web_serviceserviceId

Write actions (4)

They change things. Gate the sensitive ones with approval policies; approvals are single-use.

ActionFunctionKey params

Create postgrescreate_postgresname

Get postgresget_postgrespostgresId

List postgres instanceslist_postgres_instances—

Query render postgresquery_render_postgrespostgresId, sql

Put Render in an AI coworker's hands.

Browse templates and solution packs that work with Render, or start from the problem you're trying to fix.

Browse templates

What an AI coworkercan do in Render.

Read actions (20)

Write actions (4)

Put Render in an AI coworker's hands.

What an AI coworker
can do in Render.