ActionGitHubUpdated September 2026

How do I create a GitHub issue from a workflow?

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

Create Issue in GitHub — start free All 23 GitHub actions

Create Issue 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.
Title title	string	Required	Title. Example: Bug: Login page crashes on Safari
Body body	string	Optional	Issue description (supports GitHub Markdown)
Labels labels	array	Optional	Array of label names to apply on creation. Each must match an existing repo label exactly (case-sensitive). Leave empty to create with no labels.
Assignees assignees	array	Optional	Array of GitHub usernames to assign. Each user must have push access (i.e. be a collaborator or org member). Use lowercase login, not display name.
Milestone Number milestone	string	Optional	The milestone number to associate with this issue

Sample request

{
  "owner": "e.g. acme-corp",
  "repo": "e.g. my-project",
  "title": "e.g. Bug: Login page crashes on Safari",
  "body": "## Steps to reproduce\n1. Go to /login\n2. Click Sign In\n...",
  "labels": "[\"bug\", \"good first issue\"]"
}

Returns

{
  "id": 1,
  "user": {
    "login": "johndoe"
  },
  "state": "open",
  "title": "Bug: Login page crashes on Safari",
  "number": 42,
  "html_url": "https://github.com/acme-corp/my-project/issues/42",
  "created_at": "2025-01-15T12:00:00Z"
}

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

Triggered by

Apps that pair well as the trigger for Create Issue.

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 Issue.

What does the Create Issue action do in GitHub?

Creates a new issue in a GitHub repository with title, body, assignees, labels, milestone, and project. The default write for piping bug reports or alerts into GitHub.

What inputs does Create Issue require?

Required: Repository Owner, Repository Name, 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 Issue support batch operations?

Run Create Issue 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