Connect ActiveMerge to Delighted

When something happens in ActiveMerge, Notis takes the next step in Delighted. 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 ActiveMerge to Delighted

View example

Ask for feedback after a document is signed

Use an ActiveMerge completion webhook to schedule a Delighted survey for the signer after a document is signed.

View example

Enroll document recipients in email feedback

When ActiveMerge reports a document delivery, add or update the recipient in Delighted email Autopilot with supplied contact properties.

View example

Enroll document recipients in SMS feedback

Use a document delivery webhook to add or update a recipient in Delighted SMS Autopilot with supplied details.

View example

Request feedback after a template workflow

When a template-based ActiveMerge workflow finishes, create or update the contact in Delighted and schedule a survey email.

View example

Cancel pending surveys when a document is cancelled

When an ActiveMerge cancellation webhook identifies a person, remove that person's pending Delighted survey requests.

View example

Honor a customer's email survey opt-out

Use an explicit opt-out webhook to unsubscribe a person from future Delighted email surveys.

View example

Remove a Delighted contact after an erasure request

When an authorized erasure request is confirmed in your workflow, delete the identified person and their associated Delighted data.

View example

Review Delighted responses on a schedule

Retrieve Delighted survey responses on a recurring schedule so Notis can summarize feedback and surface themes in run reports.

View example

Review bounced survey email addresses

Retrieve Delighted bounced people on a schedule and summarize the contacts that may need attention.

Supported Triggers and Actions

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

ActiveMerge triggers

Delighted actions

Recurring trigger

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

TriggerScheduled

Add Person to Autopilot Email

Adds a person to automated email surveys or updates their profile details.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Person to Autopilot SMS

Adds a person to automated SMS surveys or updates their profile details.

ActionInstant

Create or Update Person

Creates or updates a person and schedules a survey email.

ActionInstant

Delete Pending Survey Requests

Cancels all pending survey requests for a person.

ActionInstant

Delete Person

Permanently deletes a person and all associated data.

ActionInstant

Get Autopilot Email Configuration

Retrieves the current email Autopilot configuration.

ActionInstant

Get Autopilot SMS Configuration

Retrieves the current SMS Autopilot configuration.

ActionInstant

List Autopilot SMS Memberships

Lists people enrolled in SMS Autopilot.

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.