Connect Addresszen to Chmeetings

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

View example

Add a Visitor After Address Verification

Create a ChMeetings person record when a visitor's submitted address has been verified through Addresszen.

View example

Schedule a Meeting at a Verified Venue

Create a ChMeetings meeting from an event request after Addresszen validates its venue address.

View example

Invite an Attendee After Location Confirmation

Invite a person to a ChMeetings meeting when an Addresszen-backed request confirms their location details.

View example

Set a Reminder for a Confirmed Venue Meeting

Create a ChMeetings reminder for a meeting request whose venue address has been verified through Addresszen.

View example

Notify Organizers About Confirmed Locations

Send a ChMeetings notification when an Addresszen-backed intake request confirms a location that needs organizer attention.

View example

Review Upcoming ChMeetings Reminders

On a recurring schedule, list ChMeetings reminders so organizers can review upcoming follow-ups alongside Addresszen location work.

View example

Review ChMeetings People for Address Follow-Up

On a recurring schedule, retrieve ChMeetings people records and surface address details that need review against information supplied by an Addresszen process.

View example

Review ChMeetings Organizations on a Schedule

Retrieve ChMeetings organizations on a recurring schedule and summarize directory changes or follow-up needs using context supplied by your Addresszen process.

Supported Triggers and Actions

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

Addresszen triggers

Chmeetings actions

Recurring trigger

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

TriggerScheduled

Invite Meeting Attendee

Invite a new attendee to a meeting.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Attendee Details

Retrieve the details of a specific attendee.

ActionInstant

ChMeetings: Create Meeting

Create and schedule a meeting.

ActionInstant

ChMeetings: Create Organization

Create a new organization.

ActionInstant

ChMeetings: Create Reminder

Create a reminder for a meeting.

ActionInstant

Delete Meeting Attendee

Remove an attendee from a meeting.

ActionInstant

List Meeting Attendees

List the attendees of a meeting.

ActionInstant

ChMeetings: Delete Meeting

Permanently delete an existing meeting.

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.