Connect Addressfinder to Chmeetings

When something happens in Addressfinder, 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 Addressfinder to Chmeetings

View example

Add a verified contact to ChMeetings

Check an incoming contact's address and contact details with Addressfinder, then create a ChMeetings person when the record is usable.

View example

Correct a ChMeetings contact after validation

Use an incoming request to check supplied contact details with Addressfinder and update an identified ChMeetings person when a correction is clear.

View example

Review ChMeetings contacts for data quality

On a schedule, review ChMeetings people records and use Addressfinder to check available contact details, then report records needing attention.

View example

Refresh ChMeetings contacts from validated details

On a schedule, review available contact details and update clear, validated corrections for identified ChMeetings people.

View example

Verify a ChMeetings person before follow-up

When a person ID is submitted, retrieve the ChMeetings record and check its available contact details with Addressfinder for a follow-up readiness summary.

View example

Schedule a meeting from a verified contact request

Turn a submitted meeting request into a ChMeetings meeting after checking the supplied contact details and confirming the request includes meeting information.

View example

Create a meeting reminder from a validated request

Use a submitted request to create a ChMeetings reminder when the meeting reference and reminder details are supplied and the associated contact checks out.

View example

Invite a validated contact to a meeting

Check submitted contact details with Addressfinder, then invite the identified attendee to a specified ChMeetings meeting when the match is clear.

View example

Review meetings for contact readiness

On a schedule, retrieve specified ChMeetings meetings and check supplied attendee contact details with Addressfinder, reporting any readiness concerns.

Supported Triggers and Actions

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

Addressfinder 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.