Short answer: Drop the "GitHub → Update 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. |
Issue Number issue_number | string | Required | GitHub issue number — the integer shown after # in the issue URL (per-repo, not global). |
Title title | string | Optional | Title |
Body body | string | Optional | Message body content. Plain text unless the API specifies HTML/markdown. |
State state | options | Optional | State. Options: Open, Closed |
Labels labels | array | Optional | Array of label names to set on the issue. Note: this REPLACES the existing labels (it does not append). To preserve current labels, fetch them first and merge. Empty array clears all labels. |
Assignees assignees | array | Optional | Array of GitHub usernames to set as assignees. REPLACES the existing assignees, not appends. Each user must have push access. |
{"owner": "e.g. acme-corp","repo": "e.g. my-project","issue_number": "e.g. 42","title": "{{trigger.title}}","body": "e.g. Hi there, thanks for reaching out."}
{"state": "open","title": "Updated title","number": 42}
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.