Connect Active campaign to Botpress

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

View example

Start a Botpress conversation for a new campaign lead

Use an ActiveCampaign webhook to start a Botpress conversation when a lead needs immediate follow-up.

View example

Send a Botpress reply after an ActiveCampaign event

Use a campaign webhook to deliver a prepared message in an existing Botpress conversation.

View example

Refresh Botpress bot content from campaign feedback

Use webhook-supplied campaign feedback to update relevant Botpress bot content for review and use.

View example

Validate campaign webhook data before Botpress use

Check and reshape supplied ActiveCampaign event data before using it in a Botpress workflow.

View example

Check Botpress issues when campaign activity spikes

Use an ActiveCampaign webhook to prompt a Botpress issue check when a campaign needs attention.

View example

Review Botpress conversations after campaign activity

Use campaign webhook events to retrieve Botpress conversations for a focused follow-up review.

View example

Review Botpress usage alongside campaign cycles

On a recurring schedule, retrieve Botpress usage history to review workload around ActiveCampaign campaign periods.

View example

Get a scheduled Botpress usage breakdown by bot

Run a recurring per-bot usage breakdown to see invocation, storage, or AI spend metrics in one report.

View example

Check Botpress workspace quota completion rates

On a schedule, retrieve the highest quota completion rate for each workspace to help spot capacity pressure.

Supported Triggers and Actions

Notis builds workflows that link Active campaign to Botpress. A trigger fires from one place; an action lands in another.

Active campaign triggers

Botpress actions

Recurring trigger

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

TriggerScheduled

Delete File

Permanently deletes a file from a bot’s storage; this cannot be undone.

ActionInstant

Webhook trigger

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

TriggerInstant

Break Down Workspace Usage By Bot

Breaks down workspace usage by bot, including invocations, storage, and AI spending.

ActionInstant

Get Account

Retrieves details of the authenticated account.

ActionInstant

BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES

Charges unpaid invoices for a workspace and returns which payments succeeded or failed.

ActionInstant

LIST_BOT_ISSUES

Lists issues associated with a bot.

ActionInstant

Check Handle Availability

Checks whether a workspace handle is available and suggests alternatives if it is taken.

ActionInstant

LIST_CONVERSATIONS

Lists conversations so you can retrieve chat threads.

ActionInstant

BOTPRESS_CREATE_ADMIN_INTEGRATION

Creates an integration in a workspace.

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.