Connect AimTell to Customerio

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

View example

Sync AimTell Subscriber Profiles to Customer.io

Use an AimTell webhook to create or update a Customer.io person when a subscriber record changes, keeping the profile ready for relevant follow-up.

View example

Record AimTell Campaign Engagement in Customer.io

Send selected AimTell campaign engagement details to Customer.io as person events, making notification activity available for segmentation and follow-up.

View example

Apply AimTell Email Opt-Outs to Customer.io Deliveries

When an AimTell webhook reports an email opt-out request with a Customer.io delivery reference, unsubscribe the person from that delivery.

View example

Consolidate AimTell Identity Changes in Customer.io

When a trusted AimTell event reports a changed identifier, create a Customer.io alias to consolidate the previous profile into the canonical person profile.

View example

Group AimTell Subscribers by Their Organization

Use organization details supplied by an AimTell webhook to associate a Customer.io person with an existing company, account, or project group.

View example

Review Customer.io Delivery Metrics Alongside AimTell Campaigns

On a schedule, retrieve paginated Customer.io message delivery data for a chosen time window and summarize it alongside the AimTell campaign context you provide.

View example

Review Customer.io Segments Against AimTell Audience Plans

On a schedule, retrieve Customer.io segment definitions and summarize them against the audience criteria or campaign plans you supply from AimTell.

View example

Check Customer.io Newsletters Before AimTell Campaign Planning

On a schedule, list Customer.io newsletters and summarize available newsletter metadata alongside the campaign calendar or plans you provide for AimTell.

View example

Review Customer.io Transactional Templates for Notification Journeys

On a schedule, list Customer.io transactional message templates and summarize how their available metadata relates to the notification journeys you provide for AimTell.

Supported Triggers and Actions

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

AimTell triggers

Customerio actions

Recurring trigger

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

TriggerScheduled

Suppress Customer Profile

Permanently deletes a customer profile and prevents it from being added again; this action is irreversible.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Person to Group

Adds a person to a group, linking them to an organization, account, or project.

ActionInstant

Get Integrations

Lists the integrations configured in your workspace.

ActionInstant

Create Profile Alias

Merges one profile into another, moving its data to the canonical profile.

ActionInstant

Get Messages

Retrieves messages sent from your workspace and their delivery metrics.

ActionInstant

Get Segment Details

Retrieves details about a specific segment.

ActionInstant

Get Segment Membership

Retrieves the people in a specific segment.

ActionInstant

Get Segments

Lists the segments in your workspace.

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.