List Release Assets

github.list_release_assets
ActionBusiness appsconnection required

Calls GET /repos/{owner}/{repo}/releases/{release_id}/assets.

List the files attached to a release.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
GitHub
Secret shape
the GitHub personal access token
Resolved by
config.connection_id, else node.connection_id, else the tenant's sole GitHub connection

Configuration

4 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
owner
Repository owner — the user or organisation login. Supports {{ }}.
stringYes——octocat
repo
Repository name, without the owner prefix. Supports {{ }}.
stringYes——hello-world
release_id
Numeric release id whose assets to list.
stringYes——1
max_items
Stop after this many rows; further pages are followed via the Link header.
numberNo1001–1000—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_items": 100,
  "owner": "octocat",
  "release_id": "1",
  "repo": "hello-world"
}

Output

One shape.

result

FieldTypeExample
assets
The assets this step read.
array—
assets[].id
Asset id, used to delete it.
number—
assets[].name
File name of the asset.
string—
assets[].label
Display label, when one was set.
string—
assets[].size
Asset size in bytes.
number—
assets[].content_type
Media type it was uploaded with.
string—
assets[].browser_download_url
Public download URL.
string—
count
How many rows this step returned.
number—
{
  "assets": [
    {
      "browser_download_url": "",
      "content_type": "",
      "id": 0,
      "label": "",
      "name": "",
      "size": 0
    }
  ],
  "count": 0
}

See List Release Assets run in a workflow.

In a technical demo we add the GitHub connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.