Turn GitHub review comments into Miro follow-up cards
Convert detailed feedback into a visible checklist of next moves.
Trigger
New Pull Request Review Comment
Triggers when a new inline review comment is added to a specific GitHub pull request. Monitors all review comments across all reviews on the specified pull request and emits an event for each newly created comment. Edits to existing comments do not fire new events.
Action
Create App Card Item
Tool to add an app card item to a board. use when you need to push a rich preview card with custom fields into a miro board (e.g., after assembling card data).
Why this helps
Inline review comments are easy to lose once a pull request conversation becomes busy.
- Feedback stays visible
- Less re-reading
- Clearer ownership
Setup
Build it in a few focused steps.
- 1Connect GitHub and Miro to Notis once.
- 2Create a portal automation.
- 3Ask Notis to create a Miro follow-up card for each new inline review comment.
- 4Select New Pull Request Review Comment and a report channel.
- 5Add a comment on a test pull request.
Questions about this workflow
Will edited comments duplicate cards?
No. This trigger is for new review comments rather than edits.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Miro. A trigger fires from one place; an action lands in another.
GitHub triggers
Miro actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Board
Tool to create a new board. use when you need to set up a board with a specific name, description, and policies. example: "create a new board named project plan".
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete App Card Item
Tool to delete an app card item from a board. use when you need to remove an app card item created by your app after it is no longer needed.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Document Item
Tool to delete a document item from a board. use when you need to remove a document item (e.g., pdf or image) that is no longer relevant. example: "delete the document item with id 'item456' from board 'board123'."
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Delete Item
Tool to delete a specific item from a board. use when you need to remove an item (e.g., shape, sticky note) after confirming its board and item ids.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get App Card Item
Tool to retrieve a specific app card item by its id. use when you need the details of an existing app card item.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Board
Tool to retrieve details of a specific board. use when you have a board id and need to fetch its metadata.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Board Members
Tool to retrieve a list of members for a board. use when you need to list all users with access to a board after confirming its id.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Boards
Tool to retrieve accessible boards with optional filters. use when you need to list or search boards by team, project, owner, or keywords.
Connect any two apps with Notis in the middle.
Not just GitHub and Miro. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Miro.