ActionGitHubUpdated September 2026

How do I create a GitHub release with notes?

Short answer: You can create release in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub Create Release action to a workflow, map its 8 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Release in GitHub — start free All 23 GitHub actions

Create Release in GitHub — start free

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
Repository Owner owner	string	Required	GitHub repository owner — the user or organization login (the part before / in owner/repo URLs).
Repository Name repo	string	Required	GitHub repository name — the part after / in owner/repo URLs. Not the full URL.
Tag Name tag_name	string	Required	Tag Name. Example: v1.2.0
Release Title name	string	Required	Release Title. Example: v1.2.0 — Bug fixes and improvements
Release Notes body	string	Optional	Markdown release notes
Draft draft	options	Optional	Draft. Options: No, Yes
Pre-release prerelease	options	Optional	Pre-release. Options: No, Yes
Target Branch/Commit target_commitish	string	Optional	Branch or commit SHA to tag. Defaults to default branch.

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "tag_name": "e.g. v1.2.0",
  "name": "e.g. v1.2.0 — Bug fixes and improvements",
  "body": "## What's Changed\n- Fixed login redirect\n- Improved performance"
}

Returns

{
  "id": 1,
  "name": "v1.2.0",
  "draft": false,
  "html_url": "https://github.com/acme/my-project/releases/tag/v1.2.0",
  "tag_name": "v1.2.0"
}

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

Triggered by

Apps that pair well as the trigger for Create Release.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitHub

2 Google Sheets triggers

HubSpot → GitHub

18 HubSpot triggers

FAQ

Questions about Create Release.

What does the Create Release action do in GitHub?

Creates a new release for a repository with tag name, target commitish, name, body (release notes), draft, and prerelease flags. Used to automate releases from your CI pipeline.

What inputs does Create Release require?

Required: Repository Owner, Repository Name, Tag Name, Release Title. 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 run history shows the failed step with its input and the error message GitHub returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Release support batch operations?

Run Create Release inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitHub's rate limits.

More actions