Connect AimTell to Chmeetings

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

View example

Turn an AimTell campaign into a church event

When an AimTell campaign promotes a gathering, create the corresponding ChMeetings event from the details you provide or include in the request.

View example

Review AimTell subscribers against ChMeetings people

On a schedule, compare subscriber information supplied by AimTell with ChMeetings people and report possible member matches or gaps for review.

View example

Add a referred subscriber to ChMeetings

When a trusted webhook carries a person referral from an AimTell campaign, create a ChMeetings person record with the supplied name.

View example

Audit ChMeetings reminders before an AimTell push

On a schedule, list ChMeetings reminders and summarize upcoming items that may need attention before a related AimTell push campaign.

View example

Invite an attendee from an event request

When a webhook requests an invitation and supplies the meeting and attendee details, invite that person to the ChMeetings meeting.

View example

Check ChMeetings attendance before campaign day

On a schedule, list attendees for a specified ChMeetings meeting and report the current attendee picture for event communications planning.

View example

Schedule a ChMeetings reminder from a campaign plan

When an AimTell campaign plan arrives by webhook with a meeting and reminder details, schedule the corresponding ChMeetings reminder.

View example

Pull a ChMeetings event brief for campaign planning

On a schedule, retrieve a specified ChMeetings meeting and summarize its available details for a related AimTell campaign plan.

View example

Send a ChMeetings notification from a campaign request

When an authorized request calls for a ChMeetings notification and supplies its content and context, attempt to send it and report the result.

Supported Triggers and Actions

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

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