Connect Whatsapp to Addresszen

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

View example

Resolve a WhatsApp Address ID Before Shipping

When a customer sends an Addresszen suggestion ID on WhatsApp, retrieve the complete US address for delivery review.

View example

Resolve the Address a Customer Confirms

After a customer selects an interactive WhatsApp reply, resolve the Addresszen suggestion ID included in the reply context into a full US address.

View example

Check Addresszen Key Readiness from WhatsApp

When a team member asks in WhatsApp whether Addresszen is ready, check whether its connected API key is currently usable.

Supported Triggers and Actions

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

Whatsapp triggers

Addresszen actions

Recurring trigger

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

TriggerScheduled

Key Availability

Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.

ActionInstant

Webhook trigger

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

TriggerInstant

Resolve Address USA

Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.

ActionInstant

Message Status Updated

Triggers when a WhatsApp message status changes. IMPORTANT LIMITATION: WhatsApp Cloud API does not provide a native polling endpoint for message status. Status updates are ONLY delivered via webhooks in real-time. This trigger cannot directly poll the WhatsApp API for status updates. This trigger will return empty results as WhatsApp does not support this operation. To track message status updates, you must: 1. Set up a webhook endpoint to receive status notifications from WhatsApp 2. Store the webhook data in your own database 3. Use a different mechanism to query your stored webhook data For more information, see: - https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks

TriggerPolling

New Message Received

Triggered in real time when your WhatsApp Business number receives an inbound message from a customer (text, media, location, or contact). Delivered via the Cloud API webhook.

TriggerInstant

Interactive Reply Received

Triggered when a customer taps a quick-reply button or selects an option from an interactive list message you sent.

TriggerInstant

Message Template Status Update

Triggered when the review status of a WhatsApp message template changes — for example approved, rejected, or flagged — on your WhatsApp Business Account.

TriggerInstant

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.