Find a prospect's email from Slack
When a Slack channel message names a person and company for follow-up, have Notis use Icypeas to look up a single email address and report the result.
When something happens in Slack, 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 channel is created.
Do this · Action
Starts a bulk email search using names and company details.
When a Slack channel message names a person and company for follow-up, have Notis use Icypeas to look up a single email address and report the result.
When a channel message identifies a prospect and their company, use Icypeas to find a profile URL and return it to the team for a quick context check.
When a Slack channel message names a company or domain for research, use Icypeas to find its company profile URL and share the result with the team.
When a Slack message identifies a target account and the roles the team needs to reach, use Icypeas to search for matching people and report useful results.
When a Slack message captures a market, location, or company-size brief, search Icypeas for matching companies and share the shortlist for review.
When a Slack channel message requests an introduction to a named person at a known company, look up that person's email in Icypeas and report it for review.
When Slack identifies a company domain and a need to reach a shared team inbox, use Icypeas to scan for role-based email addresses and report the findings.
When Slack event notes name a speaker and their company, use Icypeas to locate a profile URL and give the team a starting point for follow-up research.
When a Slack message identifies a customer champion by name and company, use Icypeas to find their work email so an owner can follow up.
Notis builds workflows that link Slack 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 channel is created.
Starts a scan for role-based email addresses by domain or company name.
Triggers when a message is posted in a channel, excluding direct messages.
Looks up LinkedIn profile URLs for professional email addresses.
Triggers when a new direct message, including a thread reply, is sent to a user.
Retrieves bulk search files with their status and progress, with optional filters.
Triggers when a reaction is added to a message.
Retrieves up to 50 LinkedIn company or profile records per request.
Triggers when a reaction is removed from a message.
Retrieves your Icypeas subscription details and remaining credits; unavailable for managed execution.
Triggers when a bot posts a new message in a channel.
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.
Slack 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.