Short answer: Drop the "GitHub → Create Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"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\"]"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.