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.
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.
When someone stars a repository, find a likely contact email so founders can follow up with promising adopters without maintaining a manual list.
When a pull request is opened, find the author's professional profile URL to make external collaboration and partner research easier.
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.
When a repository collaborator is added, find their professional profile URL to keep onboarding, delegation, and relationship context in one run report.
When a pull request review is submitted, resolve the reviewer's profile URL to help founders remember external contributors and strategic reviewers.
When a new inline pull request comment appears, use Icypeas to discover a reliable professional email for the commenter when possible.
When new followers appear, use Icypeas to find people matching their identity and professional context for a lightweight relationship queue.
When an issue is added, search Icypeas for the issue author or a relevant person so technical triage includes relationship context.
When a new commit is added to a pull request, use Icypeas bulk profile search to resolve multiple contributors or related identities efficiently.
Notis builds workflows that link GitHub to Icypeas. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Starts a bulk email search using names and company details.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Checks the processing progress of one search item or bulk search file.
Fires when a new GitHub Actions workflow artifact is created in a repository.
Starts a scan for role-based email addresses by domain or company name.
Fires when a branch’s commits or protection status or settings change.
Looks up LinkedIn profile URLs for professional email addresses.
Fires when a new branch is created in a GitHub repository.
Retrieves bulk search files with their status and progress, with optional filters.
Fires when a GitHub check run’s status or conclusion changes.
Retrieves up to 50 LinkedIn company or profile records per request.
Fires when a GitHub check suite changes status or conclusion for a reference.
Retrieves your Icypeas subscription details and remaining credits; unavailable for managed execution.
Fires when a new code scanning alert is created in a repository.
Finds companies in the database.
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.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,700+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
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.
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.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
GitHub and Icypeas, or any other combination from 1,700+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Icypeas.