Move stuck issue discussions into a call
Some issue threads need a quick conversation. When a new comment signals that, create a structured Cal follow-up event.
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
Create phone call event
Schedules a phone call event in cal.com using existing eventtype, organization, and team ids; this action only registers the event details and does not initiate the actual phone call.
Why this helps
Important decisions get buried in long issue threads because nobody creates the next conversation.
- Shortens drawn-out technical discussions.
- Creates a concrete follow-up event from a clear signal.
- Reduces the burden of manually setting up calls.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cal to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a new GitHub issue comment indicates that a live discussion would help, create a Cal phone call event for the issue follow-up and report the result.
- 4Choose New GitHub Issue Comment and select the channel for run reports.
- 5Test with one real comment that clearly calls for a discussion.
Questions about this workflow
Will every comment create a call?
Describe the signals that should qualify in the plain-language instruction.
Does the call happen automatically?
The Cal action registers a phone call event; it does not initiate the phone call itself.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cal. A trigger fires from one place; an action lands in another.
GitHub triggers
Cal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add member to team
Adds a new member to a specified team within an organization by creating a team membership.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add organization attribute option
Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.
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.
Delete oauth client webhook
Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.
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.
Cancel booking via uid
Cancels an existing and active cal.com booking using its unique identifier (uid).
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 calendar availability
Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.
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 gcal synchronization status
Call this read-only action to verify the connection and synchronization status of a user's google calendar integration with cal.
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.
Check ics feed calendar endpoint
Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.
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.
Check Stripe status
Verifies if stripe is correctly connected to the cal scheduling system and functional for processing payments, reporting only on the integration's status.
Connect any two apps with Notis in the middle.
GitHub and Cal, 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 Cal.