Understand who is asking for help
Every issue contains both a problem and a person. Add lightweight contact research so valuable conversations do not disappear into the backlog.
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
Find People
Tool to search for people in the leads database. Use when you need to filter people by name, title, company, and other attributes.
Why this helps
Customer and partner signals in issue reports are easy to miss when the founder is focused on fixing the technical problem.
- Surface relationship context before responding.
- Separate routine bugs from strategic conversations.
- Lower the mental cost of deciding who deserves follow-up.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Icypeas to Notis once via the portal.
- 2Create an automation in the portal or ask Notis to make one by chat.
- 3Use this instruction: When a new GitHub issue is created, use Icypeas to find the requester or a relevant person using the issue identity and available company context.
- 4Select the new issue trigger, choose where run reports should arrive, and test with one real issue.
Questions about this workflow
Is this useful for public repositories?
Yes, especially when issue authors include a recognizable name, company, domain, or profile context.
Will Notis change the issue?
This workflow only runs the Icypeas research action and reports the result through your chosen channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Icypeas. A trigger fires from one place; an action lands in another.
GitHub triggers
Icypeas actions
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.
Bulk Email Search
Tool to start a bulk email search job. Use when you have up to 5000 names and domains to batch-find emails via the ICYPEAS bulk-search endpoint.
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.
Check Search Progress
Tool to check the progress of a search by its ID. Use after initiating a single or bulk search to poll for its processing status.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Domain Scan
Tool to scan a domain for role-based email addresses. Use when you need to discover all role-based emails for a specific domain.
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.
Fetch Bulk Search Info
Tool to fetch information about bulk search files. Use when you need status and pagination details after initiating bulk search operations.
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.
Fetch Subscription Information
Tool to fetch subscription and credit info. Use after obtaining a valid API key.
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.
Find Companies
Tool to search companies in Icypeas database. Use when you need to find companies matching filters like industry, location, or headcount.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Find Company URL
Tool to find a single company profile URL using a company name or domain. Use when you need to initiate a profile-URL search for a given company identifier.
Commit Event
Triggered when a new commit is pushed to a repository.
Find People
Tool to search for people in the leads database. Use when you need to filter people by name, title, company, and other attributes.
Connect any two apps with Notis in the middle.
Not just GitHub and Icypeas. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Icypeas.