Update Miro when GitHub issue status changes
Keep the plan aligned when work closes, reopens, or changes ownership.
Trigger
New Issue Event
Triggers when a new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, renamed, locked, or unlocked. Events can optionally be filtered by type. The payload includes the event type, timestamp, the actor who triggered the event, the affected issue details, and any associated commit references.
Action
Update App Card Item
Tool to update an app card item on a board. use when you need to modify properties of an existing app card item. include only fields to change.
Why this helps
A visual plan becomes stale when issue state changes stay trapped in GitHub.
- A fresher plan
- Less double entry
- Clearer progress
Setup
Build it in a few focused steps.
- 1Connect GitHub and Miro to Notis once.
- 2Create an automation in the portal.
- 3Ask Notis to update the matching Miro planning card when an issue lifecycle event occurs.
- 4Select New Issue Event and a report channel.
- 5Close or relabel a test issue.
Questions about this workflow
Can it respond to reopened issues?
Yes. Issue timeline events include reopened issues, so describe that outcome in the prompt.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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.
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'."
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 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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
Get Board
Tool to retrieve details of a specific board. use when you have a board id and need to fetch its metadata.
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 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.
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 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.
GitHub and Miro, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Miro.