Review an available phone number when a collaborator is added
When GitHub detects a new repository collaborator, Notis can check an E.164 number if one is present in the event details you receive.
Trigger
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
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
Onboarding context can be split across tools, making it harder to notice useful contact information.
- Add a phone information lookup to a collaborator event when the event contains an E.164 number.
- See Callerapi details in the run report for onboarding follow-up.
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.
- 3In one instruction, ask Notis to look for an E.164 number in available collaborator event details and request Callerapi information if present.
- 4Pick the New Repository Collaborator Added trigger and choose where run reports should go.
- 5Test with one real collaborator event and confirm the available details include a number.
Questions about this workflow
Does the collaborator event always contain a phone number?
The listed event details include the collaborator's GitHub identity and permission information, not a guaranteed phone number. This lookup only applies if an E.164 number is available in the event context.
What happens when no number is present?
Ask Notis to report that no eligible E.164 number was available and skip the Callerapi lookup.
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.
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).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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 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.