Connect Abstract to Botpress

When something happens in Abstract, 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 Abstract to Botpress

View example

Review Botpress issues with verified contact context

Use an Abstract webhook payload to validate contact details and add Botpress bot issues to a focused review.

View example

Review Botpress conversations with Abstract context

Process text from an Abstract webhook and retrieve Botpress conversations for a concise conversation review.

View example

Find a Botpress workspace for verified contact context

Validate contact details with Abstract and retrieve Botpress workspaces to help orient a request.

View example

Review Botpress file tags against processed text

Process supplied text with Abstract and retrieve Botpress file tag metadata for a focused review.

View example

Check Botpress account access and Abstract contact data

On a schedule, validate a supplied contact detail with Abstract and retrieve authenticated Botpress account details.

View example

Get a scheduled Botpress issue digest with Abstract enrichment

Periodically retrieve Botpress bot issues and validate a supplied contact detail with Abstract for a combined report.

View example

Summarize Botpress conversation themes with Abstract

On a schedule, retrieve Botpress conversations and use Abstract to process supplied review guidance into a concise analysis.

View example

Keep a recurring Botpress workspace inventory

Retrieve Botpress workspaces on a schedule and process supplied text with Abstract for context in the report.

Supported Triggers and Actions

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

Abstract 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

ActionInstant

Get Account

Retrieves details of the authenticated account.

ActionInstant

BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES

ActionInstant

LIST_BOT_ISSUES

Lists issues associated with a bot.

ActionInstant

Check Handle Availability

ActionInstant

LIST_CONVERSATIONS

Lists conversations so you can retrieve chat threads.

ActionInstant

BOTPRESS_CREATE_ADMIN_INTEGRATION

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.