Turn selected GitHub issues into coordination meetings
When a qualifying GitHub issue is created, have Notis create a ChMeetings meeting using the purpose, timing, and other details you specify.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
Why this helps
Important issues may need a live discussion, but organizing one can take several manual steps.
- Start meeting coordination from issues that need discussion.
- Use a consistent meeting purpose for qualifying issues.
- Avoid repeatedly copying issue context into a meeting request.
Setup
Build it in a few focused steps.
- 1Connect GitHub and ChMeetings once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for issue coordination.
- 3Tell Notis which issues qualify and provide the meeting purpose, timing, and required meeting details.
- 4Pick the GitHub New Issue Created trigger and choose where run reports go.
- 5Test with one real qualifying issue and review the created meeting.
Questions about this workflow
Will Notis choose a meeting time automatically?
Provide a scheduling rule or the specific time and details in your instruction. The GitHub event does not supply meeting availability.
Can every new issue create a meeting?
You can tell Notis which issues qualify, using criteria and scheduling details that make sense for your process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Chmeetings. A trigger fires from one place; an action lands in another.
GitHub triggers
Chmeetings actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite Meeting Attendee
Tool to invite a new attendee to a specified meeting. Use when you need to add attendees before the meeting begins.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Attendee Details
Tool to retrieve details for a specific attendee. Use when you have an attendee_id and need the attendee's full profile.
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.
ChMeetings: Create Meeting
Tool to create a new meeting in ChMeetings. Use when you have all meeting details and need to schedule it via the ChMeetings API.
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.
ChMeetings: Create Organization
Tool to create a new organization.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
ChMeetings: Create Reminder
Tool to create/schedule a reminder for a meeting in ChMeetings.
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 Meeting Attendee
Tool to remove an attendee from a meeting. Use after confirming attendee details.
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.
List Meeting Attendees
Tool to list attendees of a meeting. Use when you need to retrieve attendees for a specific meeting.
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.
ChMeetings: Delete Meeting
Tool to delete an existing meeting. Use when you have confirmed the meeting ID to permanently remove the meeting.
Connect any two apps with Notis in the middle.
GitHub and Chmeetings, 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 Chmeetings.