Keep important issue context from getting buried
Good decisions should survive the thread they were written in.
Trigger
New GitHub Issue Comment
Triggers when a new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload includes the comment ID, text body, author details, timestamps, and direct links to the comment on GitHub.
Action
Store Data in Dataset
Tool to store data items in a dataset. use after collecting data when you want to batch-append or update items in an existing dataset.
Why this helps
Useful customer and team context gets buried in long issue discussions and becomes hard to retrieve.
- Preserves high-value discussion context
- Creates a searchable external record
- Reduces repeated questions
Setup
Build it in a few focused steps.
- 1Connect GitHub and Apify once via the Notis portal.
- 2Create the automation with an instruction to store each new GitHub issue comment, with its surrounding issue context, in a named Apify dataset.
- 3Select New GitHub Issue Comment as the trigger.
- 4Choose the reporting channel and test with one useful comment.
Questions about this workflow
Can I archive only decision comments?
Yes. Tell Notis to store comments that contain decisions, evidence, customer details, or next steps.
Does this edit GitHub?
No. It preserves information in Apify.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Apify. A trigger fires from one place; an action lands in another.
GitHub triggers
Apify 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.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
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 Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
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 Actor Task
Tool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
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 Task Webhook
Tool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
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 Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
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.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
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.
Get Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
Commit Event
Triggered when a new commit is pushed to a repository.
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Connect any two apps with Notis in the middle.
Not just GitHub and Apify. 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 Apify.