Start a watchlist screen from a deliberate GitHub review label
A label can mark the moment a counterparty review is ready. Notis can retrieve the existing issue details, use only an explicitly named customer or transaction party, and request an Enigma watchlist screen for human review.
Trigger
GitHub Issue Labels Changed
Triggers when the labels on a specific GitHub issue change. Fires whenever a label is added to, removed from, or has its metadata (color, description) modified on the monitored issue. The payload includes: - ``current_labels`` -- the full set of labels currently on the issue - ``added_labels`` -- labels that were newly added - ``removed_label_names`` -- names of labels that were removed - ``changed_label_names`` -- labels whose metadata changed without being added or removed
Action
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.
Why this helps
A screening request can be buried in issue activity, while starting a separate lookup by hand adds another step to an already sensitive review.
- Use a dedicated label as a clear signal that a screening request is ready.
- Screen a customer or transaction party named in the existing issue instead of inferring a person from GitHub identity.
- Return screening results for authorized review without automatically approving or rejecting a party.
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 retrieve the issue after the dedicated screening label is added and screen only an explicitly identified customer or transaction party.
- 3Choose the issue labels changed trigger for the target issue and select a channel for run reports.
- 4Test with one real issue containing the approved counterparty details, add the label, and review the Enigma result before taking action.
Questions about this workflow
Does the label-change event provide the counterparty name?
The trigger description guarantees current and changed label details, not the full issue text. Have Notis retrieve the existing GitHub issue and proceed only when it contains an explicit customer or transaction party to screen.
Does this automatically block or approve a customer?
No. Enigma returns screening results. This action does not make a business decision or change GitHub, customer, or transaction records.
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.