Add market context to new automation
A new workflow often signals a new integration, customer need, or operating pattern. Capture the companies connected to that opportunity automatically.
Trigger
New GitHub Actions Workflow Added
Triggers when a new GitHub Actions workflow is added to a repository. Monitors a repository's GitHub Actions workflows and fires an event for each newly added workflow. The payload includes the workflow's name, file path, state, creation and update timestamps, and URLs for the API, web interface, and status badge.
Action
Find Companies
Tool to search companies in Icypeas database. Use when you need to find companies matching filters like industry, location, or headcount.
Why this helps
New automation expands the business surface area, but the founder has no easy prompt to research who it may serve.
- Spot commercial context in technical changes.
- Create a lightweight research cue for new integrations.
- Reduce the chance that useful opportunities stay invisible.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Icypeas once through the Notis portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When a new GitHub Actions workflow is added, use Icypeas to find companies relevant to the workflow's integration, operational use case, or repository context.
- 4Choose the new workflow added trigger, select the run-report channel, and test with one workflow.
Questions about this workflow
Is this for every workflow?
It is most useful for workflows that represent customer-facing integrations, delivery processes, or partner operations.
Can the search use the workflow name?
Yes, the plain-language instruction can ask Notis to use the workflow name and repository context.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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.
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.
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.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Fetch Subscription Information
Tool to fetch subscription and credit info. Use after obtaining a valid API key.
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.
Find Companies
Tool to search companies in Icypeas database. Use when you need to find companies matching filters like industry, location, or headcount.
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.
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.
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 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.
GitHub and Icypeas, 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 Icypeas.