Connect Addressfinder to Breeze

When something happens in Addressfinder, Notis takes the next step in Breeze. 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 Breeze

View example

Turn Address Checks into Breeze Review Tasks

Validate submitted addresses and contact details with Addressfinder, then create Breeze cards for records that need human review.

View example

Create Follow-up Tasks for Verified Contacts

Check submitted contact details and create Breeze tasks for records that pass the requested validation criteria and are ready for follow-up.

View example

Create Breeze Projects from Clean Intake

Check an incoming project request's submitted address and contact details, then create a Breeze project when the request meets your stated data-quality requirements.

View example

Review Active Projects Against Contact Checks

On a recurring schedule, review active Breeze projects and use Addressfinder to check contact details supplied in the automation context, then report project follow-up needs.

View example

Route Data Quality Findings to Breeze

Check submitted business or contact information with Addressfinder and create a Breeze card that summarizes the data-quality issue and the requested next step.

View example

Review Breeze Tasks Alongside Contact Checks

On a recurring schedule, retrieve cards from a selected Breeze project and use Addressfinder to check the contact details supplied for the related work, then report items needing follow-up.

View example

Add an Intake Stage After Contact Verification

When a submitted intake request passes the contact checks you define, create a named Breeze project stage to organize incoming work.

View example

Check Breeze Workspaces Before Routing Intake

Retrieve available Breeze workspaces when an intake request arrives, check its submitted contact details with Addressfinder, and report which workspace is available for the next project decision.

Supported Triggers and Actions

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

Addressfinder triggers

Breeze actions

Recurring trigger

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

TriggerScheduled

Add Project People

Invites people to join a project.

ActionInstant

Webhook trigger

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

TriggerInstant

Archive Project

Archives a project to hide it from active views.

ActionInstant

Create Card

Creates a task card in a project.

ActionInstant

CREATE_LIST

Creates a new stage in a project.

ActionInstant

Create Project

Creates a new project.

ActionInstant

Create Workspace

Creates a new workspace.

ActionInstant

Delete Card

Permanently deletes a card; this action cannot be undone.

ActionInstant

Delete Project

Deletes a project.

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.