Get contact context for issues assigned to you
When an issue lands in your queue, request enrichment for any useful contact details it includes.
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
Enrich Leads
Tool to create a lead enrichment request for work emails and direct phone numbers. Uses waterfall enrichment across multiple data providers for higher accuracy. Supports batches of 1-100 leads.
Why this helps
Issues that need customer or partner follow-up can require a separate round of contact research before work can begin.
- Request enrichment when a follow-up issue reaches you.
- Reduce context switching between issue triage and contact lookup.
- Use a consistent process for contact details found in issue context.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bettercontact once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe the outcome in one instruction: extract relevant contact details available in the newly assigned issue and request Bettercontact enrichment.
- 4Pick the GitHub New Issue Assigned to Me trigger, then choose where run reports go.
- 5Test with one real assigned issue and review the enrichment request.
Questions about this workflow
Will this work if the issue has no contact details?
Enrich Leads needs usable lead details. If the issue lacks them, the workflow may not have enough information to request enrichment.
Does this assign or change the issue?
No. The selected Bettercontact action requests enrichment; it does not modify GitHub issue fields.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bettercontact. A trigger fires from one place; an action lands in another.
GitHub triggers
Bettercontact actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Credits Balance
Tool to check the remaining credits balance for a BetterContact account. Use when you need to verify available credits before making API requests that consume credits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Lead Finder Search
Tool to create a new Lead Finder search to discover leads based on company and people criteria. Use when you need to find prospects matching specific job titles, departments, seniority, company size, industry, or technology stack.
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.
Enrich Leads
Tool to create a lead enrichment request for work emails and direct phone numbers. Uses waterfall enrichment across multiple data providers for higher accuracy. Supports batches of 1-100 leads.
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 Enrichment Results
Tool to retrieve enrichment results for a specific request ID. Use when you need to check the status and get enriched lead data including email addresses, contact information, and summary statistics for a submitted enrichment request.
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 Lead Finder Results
Tool to retrieve results from a submitted Lead Finder search. Returns comprehensive lead and company data including contact information, LinkedIn profiles, job titles, company details, and enrichment data.
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 Bettercontact, 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 Bettercontact.