Skip to content
Notis

Understand the companies behind new GitHub collaborators

Get company-domain leads for new collaborators without leaving your GitHub workflow.

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

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

Why this helps

New collaborators can arrive without context, leaving founders to manually investigate their organization.

  • Reduce manual background research when repository access changes.
  • Surface likely company domains for follow-up or context.
  • Keep collaborator changes connected to a useful research step.

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Bigpicture io once in the Notis portal.
  • 2Create an automation by telling Notis the outcome you want, in a channel or in Automations, New Automation.
  • 3In one instruction, ask Notis to use the collaborator's available company name to find up to three likely domains with Bigpicture io.
  • 4Pick the New Repository Collaborator Added trigger and choose where run reports go.
  • 5Test with one real collaborator event; provide a company name if the event does not include one.

Questions about this workflow

Does GitHub provide a collaborator's company name?

The event description lists username and account details, but does not guarantee a company name. Supply one if it is not present.

How many domains can Bigpicture io return?

Name to Domain Search can find up to three likely domains from a company name.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

GitHub triggers

Bigpicture io actions

Recurring trigger

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

TriggerScheduled

Company Find

Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.

ActionInstant

Webhook trigger

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

TriggerInstant

IP to Company Lookup

Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.

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

Name to Domain Search

Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.

ActionInstant

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 Bigpicture io, 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 Bigpicture io.