Check phone examples in new GitHub pull request descriptions
When a new GitHub pull request arrives, Notis can check a phone number explicitly labeled in its description and report Veriphone’s result.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
Verify Phone Number
Tool to verify if a phone number is valid. use when you need to confirm formatting, region, and carrier details.
Why this helps
Reviewers can overlook malformed phone examples in a pull request description while focusing on other review details.
- Spot malformed phone examples stated in the PR description.
- Give reviewers a verification result alongside the pull request.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Veriphone to Notis once in the portal.
- 2Open Automations -> New Automation, or ask Notis to create this automation in plain language.
- 3Give Notis the instruction below and select the GitHub trigger named for this workflow.
- 4Choose where Notis should report each run, then test it with one real example containing a phone number.
- 5Instruction: “When a new pull request is created, inspect only its description for a phone number explicitly labeled as a test fixture or contact-flow example. If found, verify it with Veriphone and report the result and pull request link. Do not infer a number from files or other sources.”
Questions about this workflow
Does this validate numbers in the code diff?
This workflow checks only an explicitly labeled phone number in the pull request description. It does not inspect changed files.
Does this change anything in GitHub?
No. Notis asks Veriphone to check the phone number and reports the result; this workflow does not edit the GitHub item.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Veriphone. A trigger fires from one place; an action lands in another.
GitHub triggers
Veriphone actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Example Phone Number
Tool to retrieve an example phone number for a specified country and type. use after confirming the country code. example: 'get an example mobile number for us'.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Verify Phone Number
Tool to verify if a phone number is valid. use when you need to confirm formatting, region, and carrier details.
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.
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.
GitHub and Veriphone, 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 Veriphone.