Turn important issue conversations into deeper evidence
A changed comment can be the clue that deserves a closer customer look.
Trigger
GitHub Issue Comment Changed
Triggers when a specific GitHub issue comment changes. Monitors the following fields for changes: - ``body`` -- the text content of the comment (detects edits) - ``updated_at`` -- the last-updated timestamp - ``reactions_*`` -- all individual reaction counts (thumbs up/down, laugh, confused, heart, hooray, eyes, rocket) and the total count When a change is detected, the payload includes the full current comment data plus a ``changed_fields`` list indicating exactly which fields were modified.
Action
Get Dataset Feedback By ID
Retrieves a single feedback item by its unique identifier from a specific dataset. Use this tool when you need detailed information about a specific feedback item. First obtain the dataset_id using List Datasets, then get feedback_id values using Get Dataset Feedback. **Important Notes:** - Returns a warning in metadata if the feedback item doesn't exist (with null field values) - Returns 404 error if the dataset_id itself is invalid or inaccessible - The response includes feedback fields, tags, scores, timestamps, and associated metadata
Why this helps
Important clarifications and reactions in issue discussions are easy to overlook or investigate too late.
- Focuses attention on meaningful conversation changes
- Links internal discussion to concrete feedback
- Reduces manual lookup during investigation
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mopinion to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it by message.
- 3Tell Notis to retrieve the specified Mopinion feedback item related to the changed issue comment and explain how its details support or challenge the discussion.
- 4Choose the issue comment changed trigger and select a run-report channel.
- 5Test by editing one monitored comment or adding a reaction.
Questions about this workflow
Why retrieve one feedback item instead of a report?
Use this when the issue discussion points to one known response that needs detailed inspection.
Can it handle an unavailable feedback item?
Yes. Ask Notis to report missing or inaccessible feedback clearly.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mopinion. A trigger fires from one place; an action lands in another.
GitHub triggers
Mopinion actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account
Tool to retrieve the current authenticated account information. Use to verify authentication and get account details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Dataset by ID
Retrieve complete metadata for a specific Mopinion dataset (feedback form) by its ID. Returns dataset properties including name, associated report ID, data source type, and description. Use this action when you need detailed information about a specific dataset/form. To discover available dataset IDs, use the List Datasets action first. This is a read-only operation that does not modify any data.
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.
Get Dataset Feedback
Retrieve feedback items (survey responses) for a specific dataset/form with optional pagination and filtering. Use this action to fetch multiple feedback entries from a dataset. Each feedback item contains the survey responses including custom fields, scores, metadata, and timestamps. Supports pagination for large result sets and filtering by field values. For retrieving a single feedback item by ID, use GET_DATASET_FEEDBACK_BY_ID instead.
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.
Get Dataset Feedback By ID
Retrieves a single feedback item by its unique identifier from a specific dataset. Use this tool when you need detailed information about a specific feedback item. First obtain the dataset_id using List Datasets, then get feedback_id values using Get Dataset Feedback. **Important Notes:** - Returns a warning in metadata if the feedback item doesn't exist (with null field values) - Returns 404 error if the dataset_id itself is invalid or inaccessible - The response includes feedback fields, tags, scores, timestamps, and associated metadata
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 Dataset Field Definitions
Tool to retrieve field definitions for a dataset. Use when you need the schema of a dataset's fields.
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 Deployment by ID
Retrieves detailed configuration for a specific feedback form deployment by its ID. Returns deployment rules, trigger conditions, scheduling settings, target URLs, and active status. Use this to understand when, where, and how a feedback form is displayed to users.
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 Deployments
Tool to list all deployments for the authenticated Mopinion account. Use after setting up authentication.
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 Report By ID
Retrieves detailed information about a specific Mopinion report by its ID. Returns comprehensive report details including name, description, language, creation date, and all associated datasets with their metadata. Use this when you need full information about a specific report. To find available report IDs, use the Get Reports action first. Example use case: Get complete details of report 22511 to understand its datasets and configuration.
Connect any two apps with Notis in the middle.
GitHub and Mopinion, 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 Mopinion.