Find contact emails from Linear prospect issues
When a new Linear issue identifies a named prospect and company, ask Icypeas to find the person's work email so the next step does not get lost in issue triage.
When something happens in Linear, 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
Triggers when a new comment is received.
Do this · Action
Starts a bulk email search using names and company details.
When a new Linear issue identifies a named prospect and company, ask Icypeas to find the person's work email so the next step does not get lost in issue triage.
When a Linear issue is updated to indicate a lead is qualified, use Icypeas to resolve the prospect's profile URL for easier review and research.
When a lead's Linear issue is updated to indicate outreach readiness, ask Icypeas for the prospect's email so the founder can prepare the next step without another research detour.
When a comment adds a market or company-search request to a Linear issue, use Icypeas to find companies matching the described criteria and return candidates for review.
When a new Linear issue names an account and describes the role needed, use Icypeas Find People to identify relevant contacts for the team to review.
When a new project is created for market expansion or partner research, use its context to find relevant companies in Icypeas for a shortlist to review.
When a Linear project is updated with a company or partner to investigate, ask Icypeas to find the company's profile URL for a clean starting point.
When a Linear project update identifies a company and its public LinkedIn company URL, ask Icypeas to scrape the company profile and return details for project research.
When a public Linear issue update adds several named prospects, use Icypeas bulk profile URL search to resolve their profile links in one batch.
Notis builds workflows that link Linear 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.
Triggers when a new comment is received.
Starts a scan for role-based email addresses by domain or company name.
Triggers when a new issue is created.
Looks up LinkedIn profile URLs for professional email addresses.
Triggers when an issue is updated, such as when its labels or status change.
Retrieves bulk search files with their status and progress, with optional filters.
Fires when a comment is posted on an issue in a private Linear team.
Retrieves up to 50 LinkedIn company or profile records per request.
Fires when an issue is created in a private Linear team.
Retrieves your Icypeas subscription details and remaining credits; unavailable for managed execution.
Fires when an issue’s properties change in a private Linear team.
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.
Linear 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.