Connect Agentql to Delighted

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

View example

Invite launch customers to share feedback

After a launch, use AgentQL to identify customers who publicly discuss trying the product, then add eligible contacts to Delighted and schedule a survey.

View example

Review public NPS signals alongside survey responses

On a recurring schedule, use AgentQL to find public customer sentiment and retrieve Delighted survey responses for a weekly feedback review.

View example

Enroll public advocates in email survey follow-up

When a webhook signals a new public case study or customer story, use AgentQL to check the source and add an eligible contact to Delighted email Autopilot.

View example

Cancel pending surveys after a public opt-out request

On a schedule, use AgentQL to check a specified public support or preference page for clearly stated survey opt-out requests, then cancel pending Delighted surveys for verified contacts.

View example

Ask newly identified support contacts for feedback

When a webhook starts a support follow-up, use AgentQL to review the referenced public support context and add a verified contact to Delighted with a survey invitation.

View example

Audit Delighted contacts against public customer signals

Run a scheduled audit that uses AgentQL to find public customer status signals and retrieves Delighted contacts for a review report, without changing records.

View example

Honor a verified survey opt-out request

When a webhook references a public opt-out request, use AgentQL to verify the request and contact, then unsubscribe that person from Delighted email surveys.

Supported Triggers and Actions

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

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