Connect Ably to Dripcel

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

View example

Route Ably customer signals to Dripcel replies

When an Ably webhook carries a customer or conversation signal, search Dripcel replies for matching context and return the relevant replies for follow-up.

View example

Review Dripcel deliveries from an Ably reporting schedule

On a recurring schedule, retrieve Dripcel deliveries and summarize the returned records for a concise delivery review.

View example

Look up Dripcel send logs from an Ably event

Use an Ably webhook carrying a phone number, campaign, or other search detail to find relevant Dripcel SMS send logs.

View example

Get a scheduled overview of Dripcel campaigns

Retrieve the Dripcel campaign list on a recurring schedule and summarize the campaign information returned.

View example

Check a Dripcel contact from an Ably signal

When an Ably webhook includes a contact's cell number, retrieve that Dripcel contact's available details for review.

View example

Summarize Dripcel sales on a schedule

Retrieve Dripcel sales on a recurring schedule and summarize the returned sales data for review.

View example

Check Dripcel tags referenced by an Ably event

When an Ably webhook mentions a tag or contact organization task, retrieve the current Dripcel tag list for reference.

View example

Check Dripcel credits before campaign work

Retrieve the current Dripcel credit balance on a recurring schedule and include the result in a Notis run report.

View example

Check SMS eligibility for numbers in an Ably event

Use phone numbers included in an Ably webhook to check whether they are allowed to receive SMS under Dripcel opt out and targeting rules.

Supported Triggers and Actions

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

Ably triggers

Dripcel actions

Recurring trigger

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

TriggerScheduled

Delete Contact

Delete a contact.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contacts in Bulk

Creates up to 100,000 new contacts in bulk; existing contacts are not updated.

ActionInstant

Get Dripcel Campaigns

List campaigns and their statuses.

ActionInstant

Get current credit balance

Retrieve the current credit balance for your organization.

ActionInstant

Delete Tag

Deletes a tag and removes it from every contact and campaign using it.

ActionInstant

Get Deliveries

Retrieve SMS and email delivery records.

ActionInstant

Get email templates

List email templates in your account.

ActionInstant

Get sales

Retrieve sales data for reporting or analysis.

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.