Save README changes as Productboard documentation notes
Keep major product documentation changes visible to planning without another status meeting.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Create Note (v2)
Tool to create a new note in Productboard using the v2 API. Use when you need to create simple text notes or conversation-style notes with optional relationships to customers, companies, or external links.
Why this helps
Documentation updates can signal product shifts that the roadmap never captures.
- Surfaces product changes
- Creates a change record
- Cuts update meetings
Setup
Build it in a few focused steps.
- 1Connect GitHub and Productboard to Notis once.
- 2Create an automation in the portal.
- 3Tell Notis to save meaningful README changes as Productboard documentation notes.
- 4Choose GitHub Repository README Changed and a report channel.
- 5Edit the monitored README once to test it.
Questions about this workflow
Can I monitor one repository?
Yes. Select the repository when configuring the trigger.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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 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.
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.
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.
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 Component
Tool to create a new (sub)component under a product or component. Use after determining the parent component ID.
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 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.
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 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.
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 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.
GitHub and Productboard, 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 Productboard.