Tag Productboard notes when GitHub issues close
Give your product evidence a clear resolution signal without chasing updates.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Add Note Tag
Adds a tag to a Productboard note for categorization and organization. Use this action to apply tags to notes based on their content, priority, source, or any other classification criteria. Tags help organize and filter notes in Productboard. If the specified tag doesn't exist in the workspace, it will be automatically created. Tags are case-sensitive. Common use cases: - Categorize notes by priority (e.g., "Urgent", "High Priority") - Label feature requests vs. bugs (e.g., "feature-request", "bug") - Mark notes for review stages (e.g., "needs review", "approved") - Associate notes with time periods (e.g., "Q1-2026", "Sprint-5")
Why this helps
It is hard to tell which feedback has been addressed after shipping work.
- Shows progress clearly
- Reduces status hunting
- Keeps feedback organized
Setup
Build it in a few focused steps.
- 1Connect GitHub and Productboard to Notis once.
- 2Create a new automation in the portal.
- 3Ask Notis to tag the related Productboard note when an issue is closed.
- 4Select Issue State or Properties Changed and a report channel.
- 5Close one real issue to test it.
Questions about this workflow
Does this require a mapping screen?
No. Notis follows the relationship you describe in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Productboard. A trigger fires from one place; an action lands in another.
GitHub triggers
Productboard 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.
Add Note Followers
Tool to add multiple followers to a Productboard note. Use when you need to bulk-add existing users as followers to a specific note by their email addresses.
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.
Add Note Tag
Adds a tag to a Productboard note for categorization and organization. Use this action to apply tags to notes based on their content, priority, source, or any other classification criteria. Tags help organize and filter notes in Productboard. If the specified tag doesn't exist in the workspace, it will be automatically created. Tags are case-sensitive. Common use cases: - Categorize notes by priority (e.g., "Urgent", "High Priority") - Label feature requests vs. bugs (e.g., "feature-request", "bug") - Mark notes for review stages (e.g., "needs review", "approved") - Associate notes with time periods (e.g., "Q1-2026", "Sprint-5")
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Company in Productboard
Tool to create a new company in Productboard. Use when you need to add a company record after gathering its details and optional metadata.
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.
Create Company Custom Field
Tool to create a new custom field for companies. Use when you need to define custom company attributes in Productboard after confirming the field schema.
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.
Create Component
Tool to create a new (sub)component under a product or component. Use after determining the parent component 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.
Create Entity Relationship
Tool to create a relationship between two entities in Productboard. Use when you need to establish a parent, child, link, or dependency relationship between entities.
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.
Create Entity (v2)
Tool to create a new entity in Productboard using the v2 API. Use when you need to create products, components, features, subfeatures, initiatives, objectives, key results, releases, or release groups.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Feature
Tool to create a new feature or subfeature in Productboard. Use when you need to add a feature to a product or component, or create a subfeature under an existing feature.
Connect any two apps with Notis in the middle.
Not just GitHub and Productboard. 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 Productboard.