Connect Adrapid to Addressfinder

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

View example

Verify campaign emails before an Adrapid launch

Check email addresses found in an Adrapid campaign export before the campaign is released.

View example

Check phone CTAs in Adrapid campaigns

Verify phone numbers included in an Adrapid creative or campaign export before publishing call-focused ads.

View example

Standardize Australian addresses in campaign creative

Verify Australian addresses that appear in Adrapid location ads, brochures, or landing-page creative exports.

View example

Find international locations referenced by Adrapid

Search partial international address text from an Adrapid export and return matching Addressfinder IDs for review.

View example

Enrich selected international campaign locations

Retrieve full metadata for address IDs selected from an Adrapid campaign export.

View example

Add Australian location metadata to Adrapid assets

Retrieve metadata for selected Australian address IDs referenced by an Adrapid export.

View example

Suggest Australian locations from campaign copy

Autocomplete Australian streets, suburbs, or states mentioned in an Adrapid export for human review.

View example

Detail selected Australian locations for campaign review

Retrieve comprehensive metadata for Australian location IDs selected from an Adrapid export.

View example

Review New Zealand addresses in a supplied export

On a schedule, verify exact New Zealand addresses from a current Adrapid export and flag corrections.

Supported Triggers and Actions

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

Adrapid triggers

Addressfinder actions

Recurring trigger

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

TriggerScheduled

AU Address Autocomplete

Finds matching Australian addresses as you enter an address.

ActionInstant

Webhook trigger

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

TriggerInstant

Get AU Address Metadata

Retrieves detailed information about a selected Australian address.

ActionInstant

AU Address Verification

Checks and standardizes an Australian address.

ActionInstant

AU Location Autocomplete

Suggests matching Australian streets, suburbs, and states as you type.

ActionInstant

Get AU Location Metadata

Retrieves detailed information about a selected Australian location.

ActionInstant

Email Verification API

Checks whether an email address is valid and can receive messages.

ActionInstant

International Address Autocomplete

Suggests matching addresses in supported countries as you type.

ActionInstant

Get International Address Metadata

Retrieves detailed information about a selected international address.

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.