Skip to content
Notis

Check phone numbers mentioned during code review

When an inline review comment includes an E.164 phone number, have Notis request Callerapi details for a focused follow-up.

Trigger

New Pull Request Review Comment

Triggers when a new inline review comment is added to a specific GitHub pull request. Monitors all review comments across all reviews on the specified pull request and emits an event for each newly created comment. Edits to existing comments do not fire new events.

Action

Get Phone Number Information

Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).

Why this helps

Review discussions move quickly, and an operational phone number can be overlooked among code feedback.

  • Bring reputation and carrier information into the run report for review.
  • Keep number checks close to the code discussion that prompted them.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Callerapi once in the Notis portal.
  • 2Create an automation in Automations, or tell Notis from any channel what outcome you want.
  • 3Ask Notis in one instruction to find E.164 phone numbers in new inline review comments and request Callerapi information.
  • 4Pick the New Pull Request Review Comment trigger and choose where run reports should go.
  • 5Test with one real review comment containing an E.164 number.

Questions about this workflow

Does it monitor every pull request?

The listed trigger is for new inline review comments on a specific pull request. Choose that trigger for the pull request you want to monitor.

What information can Callerapi return?

Callerapi can return phone reputation, business and carrier details, and FTC complaints for a specific E.164 number.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Callerapi. A trigger fires from one place; an action lands in another.

GitHub triggers

Callerapi actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Phone Number Information

Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get User Information

Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.

ActionInstant

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.

TriggerPolling

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.

TriggerPolling

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and Callerapi, 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 Callerapi.