Connect Adrapid to Callpage

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

View example

Request a Callpage callback when an Adrapid banner launches

Use an Adrapid webhook carrying a published banner campaign and callback request details to initiate a Callpage call or schedule it.

View example

Create a Callpage widget for a new Adrapid campaign

When an Adrapid webhook supplies campaign site details, create a Callpage widget with the requested URL and configuration.

View example

Update a Callpage widget when Adrapid campaign settings change

Apply supplied Adrapid campaign URL, language, description, or enabled-state changes to an existing Callpage widget.

View example

Create a Callpage user for an Adrapid campaign owner

Create a Callpage user from an Adrapid webhook that supplies the owner's name, phone, email, and role.

View example

Assign a Callpage manager for an Adrapid campaign

Use supplied Adrapid campaign ownership data to create a manager assignment for an existing Callpage widget.

View example

Add campaign managers to a Callpage widget

Add one or more supplied Callpage users as managers for the widget associated with an Adrapid campaign.

View example

Create a Callpage SMS notification for an Adrapid campaign

Create a custom Callpage SMS message from an Adrapid webhook containing the widget, event, and exact message content.

View example

Update Callpage SMS copy from an Adrapid revision

Update an existing custom Callpage SMS message when an Adrapid webhook supplies revised copy and the exact widget message id.

View example

Create a Callpage voice message for an Adrapid campaign

Create a custom Callpage voice message using the widget, locale, and exact greeting supplied with an Adrapid campaign webhook.

Supported Triggers and Actions

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

Adrapid triggers

Callpage actions

Recurring trigger

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

TriggerScheduled

Get All Managers

Retrieves the managers assigned to a widget.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Users to Widget

Adds users as widget managers or updates an existing user-widget assignment.

ActionInstant

Get All SMS Messages

Retrieves all default and custom SMS messages for a widget.

ActionInstant

Create SMS Message

Creates custom SMS messages for widget call events.

ActionInstant

Get All Users

Retrieves the users in your account.

ActionInstant

Create User

Creates a new admin or manager user in the account.

ActionInstant

Get All Widgets

Retrieves the widgets in your account.

ActionInstant

Delete Manager

Deletes a manager’s assignment to a widget after both IDs are verified.

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.