Connect Addressfinder to ClickSend

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

View example

Text customers after address verification

Verify a submitted address with Addressfinder, then text the customer through ClickSend when the address is valid and the message is ready.

View example

Add verified contacts to a ClickSend list

Check contact details with Addressfinder before adding a customer to the appropriate ClickSend contact list.

View example

Check an audience before an SMS campaign

Use Addressfinder to validate submitted audience data before asking Notis to launch a ClickSend SMS campaign to an existing contact list.

View example

Build a monthly list from validated contacts

On a schedule, review the contact records you provide, validate their details with Addressfinder, and create a ClickSend list for eligible contacts.

View example

Estimate SMS cost for a verified audience

Validate the supplied audience details and estimate ClickSend SMS campaign pricing before you decide whether to send.

View example

Review ClickSend usage by subaccount

On a recurring schedule, retrieve ClickSend usage by subaccount for a specified month and year and summarize it for your chosen report channel.

View example

Remove opted-out contacts from a list

Run a scheduled cleanup to remove opted-out contacts from a specified ClickSend list using its opt-out list reference.

Supported Triggers and Actions

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

Addressfinder triggers

ClickSend actions

Recurring trigger

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

TriggerScheduled

Get Account Usage by Subaccount

Retrieves monthly account usage statistics grouped by subaccount.

ActionInstant

Webhook trigger

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

TriggerInstant

Send Account Activation Token

Sends an account activation token for verification.

ActionInstant

Verify New Account

Verify a new account with its activation token.

ActionInstant

Calculate Post Letter Price

Estimates the cost of sending physical letters without sending them.

ActionInstant

Calculate SMS Campaign Price

Estimates the cost of an SMS campaign before sending.

ActionInstant

Create Email Delivery Receipt Automation

Creates a rule that triggers actions when email delivery receipts arrive.

ActionInstant

Create Inbound Fax Automation

Creates a rule for automating actions when faxes arrive.

ActionInstant

Create Fax Delivery Receipt Automation

Creates a rule that triggers an action when a fax is delivered.

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.