Skip to content
Notis

Connect GitHub to Icypeas

When something happens in GitHub, Notis takes the next step in Icypeas. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Fires when a new GitHub Actions workflow artifact is created in a repository.

Do this · Action

Starts a bulk email search using names and company details.

Examples

Ways Notis can move work from GitHub to Icypeas

Turn New Stars Into Relevant Founder Contacts

When someone stars a repository, find a likely contact email so founders can follow up with promising adopters without maintaining a manual list.

Resolve Pull Request Author Profiles

When a pull request is opened, find the author's professional profile URL to make external collaboration and partner research easier.

Research New Issue Requesters

When a new issue arrives, use Icypeas to find relevant people matching the requester's identity or role so support and discovery follow-up is easier.

Add Context Around New Collaborators

When a repository collaborator is added, find their professional profile URL to keep onboarding, delegation, and relationship context in one run report.

Research Reviewers Behind Key Decisions

When a pull request review is submitted, resolve the reviewer's profile URL to help founders remember external contributors and strategic reviewers.

Find Contacts Behind Important Review Comments

When a new inline pull request comment appears, use Icypeas to discover a reliable professional email for the commenter when possible.

Research New GitHub Followers

When new followers appear, use Icypeas to find people matching their identity and professional context for a lightweight relationship queue.

Build Context From Added Issues

When an issue is added, search Icypeas for the issue author or a relevant person so technical triage includes relationship context.

Batch Resolve Contributors on PR Updates

When a new commit is added to a pull request, use Icypeas bulk profile search to resolve multiple contributors or related identities efficiently.

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.

TriggerScheduled

Bulk Email Search

Starts a bulk email search using names and company details.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Check Search Progress

Checks the processing progress of one search item or bulk search file.

ActionInstant

New Workflow Artifact Created

Fires when a new GitHub Actions workflow artifact is created in a repository.

TriggerPolling

Domain Scan

Starts a scan for role-based email addresses by domain or company name.

ActionInstant

Branch Changed

Fires when a branch’s commits or protection status or settings change.

TriggerPolling

Bulk Reverse Email Lookup

Looks up LinkedIn profile URLs for professional email addresses.

ActionInstant

New Branch Created

Fires when a new branch is created in a GitHub repository.

TriggerPolling

Fetch Bulk Search Info

Retrieves bulk search files with their status and progress, with optional filters.

ActionInstant

Check Run Status / Conclusion Changed

Fires when a GitHub check run’s status or conclusion changes.

TriggerPolling

Scrape Bulk

Retrieves up to 50 LinkedIn company or profile records per request.

ActionInstant

Check Suite Status / Conclusion Changed

Fires when a GitHub check suite changes status or conclusion for a reference.

TriggerPolling

Fetch Subscription Information

Retrieves your Icypeas subscription details and remaining credits; unavailable for managed execution.

ActionInstant

New Code Scanning Alert Created

Fires when a new code scanning alert is created in a repository.

TriggerPolling

Find Companies

Finds companies in the database.

ActionInstant
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect GitHub and Icypeas

Connect any two apps with Notis in the middle.

GitHub and Icypeas, or any other combination from 1,700+ 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.