List Releases: GitHub action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
Results Per Page per_page	number	Optional	Results Per Page

Sample request

{
  "owner": "e.g. octocat",
  "repo": "e.g. hello-world",
  "per_page": "{{trigger.per_page}}"
}

Returns

[
  {
    "id": 1,
    "name": "v1.0.0",
    "draft": false,
    "tag_name": "v1.0.0",
    "prerelease": false,
    "published_at": "2026-01-01T00:00:00Z"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Releases.

What does the List Releases action do in GitHub?

Lists releases for a GitHub repository with tag, name, body, and published_at. Used to render a changelog page or to feed release-notes feeds.

What inputs does List Releases require?

Required: Owner, Repository. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitHub returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Releases support batch operations?

Yes. Run List Releases inside a Loop node to process arrays. Tiny Command handles GitHub's rate limits automatically so you don't have to throttle manually.

More actions