Connect AimTell to Agent mail

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

View example

Turn an AimTell campaign review request into an email draft

Create a review-ready Agent mail draft when an AimTell campaign needs approval, with the campaign details and requested decision in one place.

View example

Email the team about an AimTell delivery incident

Send a concise Agent mail alert when your monitoring or operating process reports an AimTell push delivery issue.

View example

Prepare a weekly push campaign planning email

On a schedule, create an Agent mail draft that gathers the AimTell campaign planning context you provide and frames the decisions for the week.

View example

Prepare follow-up drafts for open campaign decisions

Create a scheduled Agent mail draft that prompts you to review campaign decisions or follow-ups you have identified as still open.

View example

Draft a review note for a subscriber segment change

Create an Agent mail draft when your process reports a significant AimTell segment change that needs a human review or explanation.

View example

Send a push campaign launch confirmation

Send an Agent mail confirmation when your launch process reports that an AimTell campaign has been launched, including the supplied launch details.

View example

Prepare a monthly push performance review draft

Create an Agent mail draft for a monthly AimTell performance review using analytics or notes available to Notis and supplied by your process.

View example

Email an escalation for a push subscriber issue

Send an Agent mail escalation when your support process reports a subscriber issue that needs attention from the campaign owner.

Supported Triggers and Actions

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

AimTell triggers

Agent mail actions

Recurring trigger

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

TriggerScheduled

Get Message

Retrieves the full details of an email message from an inbox.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Draft

Create a draft and optionally schedule its automatic delivery.

ActionInstant

List Messages

Lists messages in an inbox.

ActionInstant

Create Inbox

Create an inbox for sending and receiving messages.

ActionInstant

Send Email

Sends an email.

ActionInstant

Create Inbox API Key

Create an inbox-scoped API key; omitting permissions grants all available inbox permissions.

ActionInstant

Delete Thread

Permanently delete a thread and all its messages.

ActionInstant

Get API Key

Retrieve API key details without exposing its secret.

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.