Heroku

Manage apps, dynos, config vars, and releases with the Heroku Platform API.

Detail	Value
Category	Cloud & Infra
Base URL	https://api.heroku.com
Authentication	Bearer Token
Endpoints	8
Connector key	heroku

Using Heroku in a workflow

1. Go to Connections and click New Connection.
2. Pick Heroku from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /apps	List apps
POST /apps	Create an app
GET /apps/{app_id_or_name}	Get app details
DELETE /apps/{app_id_or_name}	Delete an app
GET /apps/{app_id_or_name}/dynos	List dynos
PATCH /apps/{app_id_or_name}/formation/{formation_id_or_type}	Scale dynos
GET /apps/{app_id_or_name}/config-vars	List config vars
GET /apps/{app_id_or_name}/releases	List releases

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /apps

List apps

Detail	Value
Operation ID	cloud.listApps
Method	GET
Path	/apps

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listApps.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

POST /apps

Create an app

Detail	Value
Operation ID	cloud.createApp
Method	POST
Path	/apps

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createApp.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

GET /apps/{app_id_or_name}

Get app details

Detail	Value
Operation ID	cloud.getApp
Method	GET
Path	/apps/{app_id_or_name}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getApp.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

DELETE /apps/{app_id_or_name}

Delete an app

Detail	Value
Operation ID	cloud.deleteApp
Method	DELETE
Path	/apps/{app_id_or_name}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.deleteApp.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

GET /apps/{app_id_or_name}/dynos

List dynos

Detail	Value
Operation ID	cloud.listDynos
Method	GET
Path	/apps/{app_id_or_name}/dynos

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listDynos.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

PATCH /apps/{app_id_or_name}/formation/{formation_id_or_type}

Scale dynos

Detail	Value
Operation ID	cloud.updateFormation
Method	PATCH
Path	/apps/{app_id_or_name}/formation/{formation_id_or_type}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.updateFormation.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

GET /apps/{app_id_or_name}/config-vars

List config vars

Detail	Value
Operation ID	cloud.listConfigVars
Method	GET
Path	/apps/{app_id_or_name}/config-vars

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listConfigVars.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.

GET /apps/{app_id_or_name}/releases

List releases

Detail	Value
Operation ID	cloud.listReleases
Method	GET
Path	/apps/{app_id_or_name}/releases

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Heroku connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listReleases.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Heroku API reference.