Retrieve Chaser customer context from GitHub notifications
Put useful account context beside the notification that needs your attention.
Trigger
Repository Notification Received
Triggers when a new or newly updated notification thread appears for a specific GitHub repository. Monitors notifications for issues, pull requests, commits, releases, check suites, security alerts, and other repository activity. Supports filtering by read/unread status and by direct participation. Requires a Personal Access Token (classic) with the ``notifications``
Action
Get Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
Why this helps
A GitHub alert can demand an immediate answer while customer details are scattered elsewhere.
- Reduces app switching during urgent work
- Helps responses stay customer-aware
Setup
Build it in a few focused steps.
- 1Connect GitHub and Chaser once in Notis.
- 2Create a new automation.
- 3Describe that Notis should retrieve the relevant Chaser customer details for qualifying repository notifications.
- 4Select Repository Notification Received and a reporting channel.
- 5Trigger a real test notification.
Questions about this workflow
Can it focus on direct participation notifications?
Yes. Choose the appropriate notification filtering in the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Chaser. A trigger fires from one place; an action lands in another.
GitHub triggers
Chaser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Credit Notes
Tool to retrieve a list of credit notes. use after authenticating this detail.
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 Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
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 Customers
Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.
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 Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
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.
Create Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
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.
Create Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
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.
Update Customer
Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."
Connect any two apps with Notis in the middle.
GitHub and Chaser, 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 Chaser.