Keep new GitHub collaborators visible as companies
A new collaborator can be a relationship signal, not just an access change.
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
Create Pipeline CRM Company
Tool to create a new company in pipeline crm. use when you need to add a company after gathering its details.
Why this helps
New collaborators from partner or customer organizations can enter the codebase without being added to the relationship system.
- Creates company visibility when collaboration begins
- Reduces duplicate research and manual CRM entry
- Supports better follow-up with technical stakeholders
Setup
Build it in a few focused steps.
- 1Connect GitHub and Pipeline CRM to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: When a qualifying new GitHub repository collaborator is added, create a Pipeline CRM company using the collaborator and organization context.
- 4Select the New Repository Collaborator Added trigger, choose a channel for run reports, and test with one safe collaborator example.
Questions about this workflow
Can individual collaborators be excluded?
Yes. Tell Notis to create companies only when an organization or partner context is available.
What if the company already exists?
Ask Notis to check the available context and avoid creating a duplicate when it can identify an existing company.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Pipeline crm. A trigger fires from one place; an action lands in another.
GitHub triggers
Pipeline crm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Company
Tool to delete a company by id in pipeline crm. use after confirming the company id is correct. example: "delete company with id 123".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Deal
Tool to delete a deal by id. use when you need to remove a deal from pipeline crm.
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.
Get Company by ID
Tool to retrieve details for a specific company by id. use after you have the company id.
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.
Get Deal by ID
Tool to retrieve details for a specific deal by id in pipeline crm. use after confirming the deal id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Deal Stage by ID
Tool to retrieve details for a specific stage by id in pipeline crm. use after confirming the stage id.
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.
Get calendar task by ID
Tool to retrieve details for a specific task by id in pipeline crm. use after confirming the task id.
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.
List Companies
Tool to list companies in pipeline crm. use when you need to fetch multiple companies with optional filtering and pagination.
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.
List Leads
Tool to list leads in pipeline crm. use when you need to fetch multiple leads with optional filtering and pagination.
Connect any two apps with Notis in the middle.
GitHub and Pipeline crm, 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 Pipeline crm.