In this guide

Comment on an Issue

Add a comment to an issue or pull request.

Action referenceCreate

What this action does #

First, connect GitHub in Services. Then open Actions → + → GitHub and choose Comment on an Issue.

What a run does

Running or testing this action creates something in your connected service.

More about this action

One required field, so this is the cheapest write in the catalog and the natural second step of a chain: list issues, then comment on the first one.

Use a pull request number to comment in its conversation. Body is Markdown, and @mentions in it notify people exactly as they would from the website.

Commenting in a tight loop trips GitHub's secondary rate limit, which reports 403 rather than 429.

Inputs to fill in #

Open an input to choose its value. Keep a fixed value with Text, receive it from Shortcuts, ask when the action runs, or use an Earlier Step. Read how input sources work.

Owner

RequiredText

User or organisation.

This input offers a picker for repository from your connected account. You can also supply its value directly.

Example value (replace with your own):

octocat

Repository

RequiredText

Name only, without the owner and without .git.

This input offers a picker for repository from your connected account. You can also supply its value directly.

Example value (replace with your own):

Hello-World

Issue Number

RequiredWhole number

The number shown in the interface, not the internal id.

This input offers a picker for issue from your connected account. You can also supply its value directly.

Example value (replace with your own):

Comment

RequiredText

Markdown.

Example value (replace with your own):

Looking at this now.

What comes back #

In the action editor, open Output → Returned Value to choose fields for your shortcut. These are the response fields described by the app; a service may omit an optional field or return an empty list. JSON File contains the full response.

Returned field	Type	Meaning
`id`	integer	Needed to edit or delete this comment.
`body`	string	Markdown.
`html_url`	string	Permalink to the comment.
`created_at`	string	ISO 8601.
`updated_at`	string	Differs from created_at once edited.
`author_association`	string	OWNER, MEMBER, COLLABORATOR, CONTRIBUTOR or NONE.
`user`	object	Who wrote it.
`user.login`	string	Username.
`user.id`	integer	Whole-number value.
`user.html_url`	string	Their profile page.
`user.avatar_url`	string	Text value.
`user.type`	string	User, Organization or Bot.

Run it from Shortcuts #

Give the action a recognizable name and tap Save.
In Apple Shortcuts, add Shortcutify’s Execute Action and select the saved action.
Supply any Param or File slots you bound in the inputs, then run the shortcut.

If the result is unexpected, open Logs in Shortcutify, select the run, and inspect this step’s inputs and response.

Advanced reference #

Request, permissions, and identifiers

Request: POST https://api.github.com/repos/{owner}/{repo}/issues/{issue_number}/comments

Action identifier: github.issues.comments.create.v1

Permissions declared for this action: issues:write. The account’s own access rules also apply.

Input	Request key	Location
Owner	`owner`	path
Repository	`repo`	path
Issue Number	`issue_number`	path
Comment	`body`	body

GitHub API reference