Connect AimTell to Calendarhero

When something happens in AimTell, Notis takes the next step in Calendarhero. 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 Calendarhero

View example

Turn an AimTell opt-in into a meeting request

When a subscriber asks to meet through an AimTell-linked form or webhook, use their submitted details to create a CalendarHero meeting request.

View example

Save an AimTell subscriber as a CalendarHero contact

Create a CalendarHero contact when a webhook carries a subscriber's contact details and a clear reason to add them.

View example

Ask CalendarHero's assistant about a campaign response

Pass an AimTell webhook's question or scheduling request to the CalendarHero assistant and return its response for review.

View example

Send a CalendarHero reminder after an AimTell request

When an AimTell-linked request identifies a scheduled CalendarHero meeting and asks for a reminder, send the reminder using its meeting task ID.

View example

Review CalendarHero meetings during an AimTell campaign week

On a chosen campaign schedule, retrieve CalendarHero meetings for the specified period and summarize the calendar load for planning.

View example

Check open CalendarHero meeting tasks for campaign follow-up

On a recurring schedule, retrieve active or upcoming CalendarHero meeting tasks and identify coordination items that may need attention.

View example

Check CalendarHero meeting types before an AimTell campaign

Before a campaign window, retrieve configured CalendarHero meeting types and summarize the options available for scheduling follow-up.

View example

Check connected calendars before an AimTell scheduling push

On a chosen schedule, list CalendarHero calendar connections and report whether the expected calendars appear before campaign scheduling begins.

Supported Triggers and Actions

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

AimTell triggers

Calendarhero actions

Recurring trigger

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

TriggerScheduled

Add Calendar Connection

Adds a calendar connection to organize meeting types.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Creates a new contact.

ActionInstant

Create Meeting Request V2

Creates a meeting request with participants and scheduling details.

ActionInstant

Fetch Contact

Retrieves a contact.

ActionInstant

Create Webhook

Creates or updates a webhook to receive event notifications.

ActionInstant

Fetch Meeting Details

Fetches meeting details for a specified time period.

ActionInstant

Delete Contact

Permanently deletes a contact.

ActionInstant

Fetch User Profile

Fetches the authenticated user's profile details.

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.