Connect Adyntel to Botpress
When something happens in Adyntel, 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
Ways Notis can move work from Adyntel to Botpress
Refresh a Botpress bot after a competitor ad review
Send an Adyntel competitor ad review to a webhook and update a Botpress bot with the relevant campaign insights.
Review bot usage alongside competitor campaigns
On a schedule, collect Botpress usage by bot and use current Adyntel campaign reports to frame a concise review of activity and competitor context.
Investigate Botpress issues with campaign context
When a webhook receives an Adyntel campaign report or ad insight, list issues for the relevant Botpress bot and summarize both for investigation.
Track Botpress usage during Adyntel campaigns
On a chosen schedule, retrieve Botpress usage history and summarize it alongside Adyntel campaign reports supplied for the same period.
Review Botpress conversations after an ad insight
Use an Adyntel insight sent to a webhook as a prompt to list Botpress conversations and summarize the relevant chat history for follow-up.
Monitor Botpress quota completion during market reviews
On a schedule, check workspace quota completion rates and summarize them with the Adyntel campaign context available for the review.
Reply to a Botpress conversation with campaign context
Use an incoming Adyntel report to draft and send a relevant reply to an existing Botpress conversation when the request clearly calls for a response.
Check Botpress quota before campaign changes
Before a planned campaign review or bot content change, use a schedule to check a specified Botpress workspace quota and report available Adyntel context.
Verify a Botpress integration for an ad workflow
When an Adyntel workflow request arrives, retrieve the relevant Botpress integration details so the team can confirm actions and configuration before relying on it.
Supported Triggers and Actions
Notis builds workflows that link Adyntel to Botpress. A trigger fires from one place; an action lands in another.
Adyntel triggers
Botpress actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete File
Permanently deletes a file from a bot’s storage; this cannot be undone.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Break Down Workspace Usage By Bot
Breaks down workspace usage by bot, including invocations, storage, and AI spending.
Get Account
Retrieves details of the authenticated account.
BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES
Charges unpaid invoices for a workspace and returns which payments succeeded or failed.
LIST_BOT_ISSUES
Lists issues associated with a bot.
Check Handle Availability
Checks whether a workspace handle is available and suggests alternatives if it is taken.
LIST_CONVERSATIONS
Lists conversations so you can retrieve chat threads.
BOTPRESS_CREATE_ADMIN_INTEGRATION
Creates an integration in a workspace.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Adyntel and Botpress
Connect any two apps with Notis in the middle.
Adyntel and Botpress, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botpress.