Connect Acculynx to Delighted

When something happens in Acculynx, 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 Acculynx to Delighted

View example

Survey customers after an Acculynx project handoff

When an Acculynx handoff is sent to Notis by webhook, create or update the customer in Delighted and schedule a survey email.

View example

Enroll eligible Acculynx leads in Delighted email Autopilot

Use an Acculynx lead webhook to add or update a person in Delighted email Autopilot with supplied properties.

View example

Enroll Acculynx leads in Delighted SMS Autopilot

Use an Acculynx lead webhook to add or update a person for scheduled Delighted SMS surveys.

View example

Cancel pending Delighted surveys when an Acculynx job is put on hold

When a hold notification reaches a Notis webhook, remove that person's pending Delighted survey requests using their email.

View example

Apply customer email opt-outs from Acculynx requests

When an opt-out request reaches a Notis webhook, unsubscribe the specified person from Delighted email surveys.

View example

Review Delighted feedback alongside Acculynx project activity

On a recurring schedule, retrieve Delighted responses and summarize them against Acculynx project context available to Notis.

View example

Reconcile Acculynx customer contacts with Delighted people

On a schedule, compare available Acculynx customer contacts with Delighted's people list and create or update records when needed.

View example

Review bounced survey contacts against Acculynx customers

On a schedule, list bounced Delighted people and compare them with available Acculynx customer contacts for a cleanup review.

View example

Review Delighted survey opt-outs against Acculynx customers

On a schedule, list Delighted unsubscribed people and compare them with available Acculynx customer contacts for visibility.

Supported Triggers and Actions

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

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