Keep research context current as issue comments change
A comment edit can correct or clarify a reported problem. Capture substantive changes in Dovetail so the evidence stays current.
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
Create Data Point
Tool to create a data point within a channel. use after capturing new content to record and classify it in dovetail.
Why this helps
Research records can preserve outdated details when issue discussions are edited after initial capture.
- Notice corrections to previously reported context.
- Keep updated evidence traceable to the issue comment.
- Reduce stale product feedback records.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dovetail once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Describe the outcome: when a monitored issue comment changes substantively, add a Dovetail data point with the updated summary and comment link.
- 4Pick the GitHub Issue Comment Changed trigger and choose where run reports go.
- 5Test with one real comment change.
Questions about this workflow
Does this monitor all GitHub comments?
The listed trigger monitors a specific issue comment. Choose the comment to monitor in the trigger setup.
Can it overwrite the earlier Dovetail entry?
Ask Notis to add a dated update. The available Dovetail action creates a data point and does not specify an edit operation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dovetail. A trigger fires from one place; an action lands in another.
GitHub triggers
Dovetail actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Channel
Tool to create a new channel in dovetail. use after confirming channel details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact in dovetail. use when you need to register a contact before logging interactions.
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 Data Point
Tool to create a data point within a channel. use after capturing new content to record and classify it in dovetail.
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 Insight
Tool to create a new insight in dovetail. use after synthesizing findings when ready to store them. example: "create insight 'q1 user trends' with body '...' for project 'proj 123'."
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 Topic
Tool to create a new topic in a channel. use after confirming channel id, title, and optional description.
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 Channel
Tool to delete an existing channel. use when you need to remove a channel and move it to the project's trash (restorable for 30 days). confirm the channel id before calling.
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.
Delete Topic
Tool to delete an existing topic. use when you have confirmed the topic id and want to move it to trash (restorable for 30 days). example: "delete topic with id 123e4567-e89b-12d3-a456-426614174000."
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 Note
Tool to retrieve details of a specific note. use when you have confirmed the note id and need full note metadata from dovetail.
Connect any two apps with Notis in the middle.
GitHub and Dovetail, 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 Dovetail.