Connect 21risk to Dripcel

When something happens in 21risk, 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 21risk to Dripcel

View example

Text owners before 21risk action deadlines

Send a targeted SMS when a 21risk action is nearing its deadline, with the action name and due date supplied in the webhook request.

View example

Check supplier numbers against campaign rules

Run a Dripcel compliance check on supplier cell numbers provided with a 21risk compliance update before proceeding with outreach.

View example

Tag contacts tied to a 21risk audit

Add a supplied audit or compliance tag to an existing Dripcel contact when a 21risk audit update identifies that contact.

View example

Send scheduled compliance task follow-ups

On a chosen schedule, review 21risk compliance tasks and send an SMS to the owner for each task that meets your follow-up criteria.

View example

Review SMS replies for compliance follow-up

On a schedule, search Dripcel replies using the date range or campaign criteria you provide after reviewing related 21risk actions.

View example

Check delivery status for compliance messages

On a schedule, retrieve Dripcel deliveries for a supplied cell number or customer ID to review whether compliance messages reached their recipients.

View example

Check Dripcel credits before planned outreach

Retrieve the current Dripcel credit balance on a schedule before planned compliance outreach, so the balance is visible during preparation.

View example

Remove a contact after a confirmed compliance request

Delete a Dripcel contact by confirmed cell number when a 21risk compliance update explicitly requests removal.

Supported Triggers and Actions

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

21risk triggers

Dripcel actions

Recurring trigger

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

TriggerScheduled

Delete Contact

Tool to delete a contact by their cell number. use when you need to remove a contact from dripcel after confirming the msisdn.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Dripcel Campaigns

Tool to retrieve a list of all campaigns. use after authenticating when you need to paginate or filter campaigns.

ActionInstant

Get current credit balance

Tool to get current credit balance. use after authenticating and when you need to verify account balance before credit-consuming operations.

ActionInstant

Get Deliveries

Tool to retrieve a list of deliveries. use when you need to fetch delivered messages optionally filtered by cell or customerid.

ActionInstant

Get email templates

Tool to list all available email templates. use when you need to retrieve available templates before sending email campaigns.

ActionInstant

Get sales

Tool to retrieve a list of all sales. use when you need comprehensive sales data for reporting or analytics.

ActionInstant

Dripcel Post Compliance Send

Tool to check a list of cell numbers against campaign targeting criteria. use when ensuring suppliers comply with your campaign rules before sending messages.

ActionInstant

Search replies based on filters

Tool to search replies based on filters. use when you need to find replies by id, campaign, date range, or content.

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.