Keep event research current as the discussion evolves
A useful comment should move the event plan forward while the conversation is active.
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
Get Event Categories
Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.
Why this helps
Important event details arrive in comments but never make it into the next planning decision.
- Captures new context without manual rereading.
- Keeps category guidance aligned with the latest discussion.
- Reduces dropped follow-up after asynchronous collaboration.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Eventbrite to Notis once through the portal.
- 2Create an automation and tell Notis: When a new comment adds meaningful event details, retrieve Eventbrite categories that fit the updated plan and report them with the comment link.
- 3Select New GitHub Issue Comment as the trigger.
- 4Choose a run-report channel and test with one planning comment.
Questions about this workflow
Can it ignore routine comments?
Yes. State in the instruction which labels, phrases, or types of comments count as meaningful event updates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Eventbrite. A trigger fires from one place; an action lands in another.
GitHub triggers
Eventbrite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Event Categories
Tool to retrieve event categories. use when selecting a category for an event. localizes results via optional locale parameter.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Event Formats
Tool to list event formats. use when you need the available formats before creating or updating an event.
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 Event Subcategories
Tool to list all event subcategories. use when fetching available subcategory options, optionally filtered by locale after selecting a category.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
Not just GitHub and Eventbrite. Any 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 Eventbrite.