Connect Addressfinder to Clearout

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Addressfinder to Clearout

View example

Verify a new email before it enters your pipeline

When an intake webhook includes an email, check its deliverability with Clearout and return the result for your next step.

View example

Audit a contact file on a schedule

On a recurring schedule, have Notis send an available contact file to Clearout for bulk email verification and report the run.

View example

Flag disposable emails at signup

When a signup webhook includes an email address, check whether it comes from a disposable provider before handling the signup.

View example

Confirm work email status before onboarding

When an onboarding request arrives, ask Clearout whether the supplied email belongs to a business account.

View example

Find emails for a prospect list on a schedule

On a recurring schedule, submit an available CSV or XLSX contact file to Clearout's bulk email finder and review the run report.

View example

Look up a company from a submitted domain

When a company domain arrives by webhook, use Clearout to retrieve the associated company profile and contact details.

View example

Add person context to a submitted email

When a webhook supplies an email, use Clearout to retrieve the associated person profile for review.

View example

Check verification credits before list work

Run a scheduled check of Clearout's available email verification credits and send the result to your chosen report channel.

View example

Suggest a domain from a company name

When an intake request includes a company name, ask Clearout for probable domain suggestions with confidence scores.

Supported Triggers and Actions

Notis builds workflows that link Addressfinder to Clearout. A trigger fires from one place; an action lands in another.

Addressfinder triggers

Clearout actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Autocomplete Company to Domain

Suggests likely website domains for a company name.

ActionInstant

Webhook trigger

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

TriggerInstant

Business Account Verify

Checks whether an email belongs to a business account.

ActionInstant

Catch-All Verify

Checks whether an email domain accepts mail for any address.

ActionInstant

Verify Disposable Email

Checks whether an email address uses a disposable provider.

ActionInstant

Find Domain MX Records

Retrieves a domain's mail server records.

ActionInstant

Fetch Domain WHOIS Information

Retrieves a domain's WHOIS information.

ActionInstant

Bulk Email Finder

Finds email addresses in bulk from a contacts file.

ActionInstant

Cancel Bulk Email Finder Job

Cancels an in-progress bulk email finding job.

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 recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ 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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

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.

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.