Turn assigned customer issues into visible commitments
If it lands on your plate, give the customer side a place to live.
Trigger
New Issue Assigned to Me
Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.
Action
Create Deal
Tool to create a new deal in pipeline crm. use after gathering all details. example: create a deal named 'big partnership' worth 50000 usd in stage 2.
Why this helps
Assigned issues can become private mental reminders that compete with product work and disappear from the weekly review.
- Creates a second view for customer-facing commitments
- Reduces the burden of remembering why an issue matters
- Makes follow-up easier to review alongside other deals
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 set it up conversationally.
- 3Use this instruction: When a GitHub issue assigned to me is a qualifying customer commitment, create a Pipeline CRM deal with the issue context and next-step suggestion.
- 4Select the New Issue Assigned to Me trigger, choose a reporting channel, and test with one assigned issue.
Questions about this workflow
Can internal issues be excluded?
Yes. Describe the labels, repositories, or customer language that identify commitments.
Why create a deal for an engineering issue?
The deal preserves the relationship and follow-up context while the issue remains the technical source of truth.
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.