Check vendor business details from the issue that requested review
When a new GitHub issue is clearly marked for vendor review and includes the legal business name, Notis can request an Enigma KYB lookup. Review the returned match and entity details before making an onboarding decision.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
KYB Business Verification
This tool performs a know your business (kyb) check on a business by querying enigma's dataset of legal entities based on official state records. it verifies business information and returns comprehensive details about the business, including best match, legal entities, brands, and watchlists.
Why this helps
Vendor review details can be scattered across issue trackers and external checks, making it easy to postpone verification or lose track of the evidence to review.
- Start a KYB lookup from an explicitly labeled business review request.
- Use the legal business name in the issue rather than trying to infer a company from its GitHub author.
- Surface Enigma's best match, legal entities, brands, and watchlist details for human review.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Enigma to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally; instruct it to run a KYB check only for a new vendor review issue that includes the legal business name.
- 3Select the new issue trigger, filter for your vendor-review label, and choose a channel for run reports.
- 4Test with one real review issue and verify the returned business match before using it in an onboarding decision.
Questions about this workflow
Can this identify a company from a GitHub username?
No. Use an explicit legal business name in the issue. A GitHub username or profile is not reliable proof of a legal entity.
Does a KYB result automatically approve a vendor?
No. The workflow retrieves Enigma verification details for review. A person should assess the match and decide what to do next.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Enigma. A trigger fires from one place; an action lands in another.
GitHub triggers
Enigma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
KYB Business Verification
This tool performs a know your business (kyb) check on a business by querying enigma's dataset of legal entities based on official state records. it verifies business information and returns comprehensive details about the business, including best match, legal entities, brands, and watchlists.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Screen Against Sanctions and Watchlists
A tool to screen customers and transactions against sanctions and other watchlists. this endpoint allows for independent verification without requiring any external resource ids.
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 Enigma, 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 Enigma.