Connect ActiveMerge to Bunnycdn

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

View example

Refresh a merged document on BunnyCDN

Purge a BunnyCDN URL when an ActiveMerge document is updated so its latest version can be served.

View example

Create a BunnyCDN storage zone for merged files

Create a dedicated BunnyCDN storage zone when an ActiveMerge workflow needs a new destination for files.

View example

Review BunnyCDN storage zones for ActiveMerge workflows

Fetch the BunnyCDN storage zone list on a schedule to make file destinations easier to review.

View example

Confirm the region for an ActiveMerge file destination

Retrieve the region code for a specified BunnyCDN storage zone when a file workflow needs a location check.

View example

Inspect a BunnyCDN storage zone before routing files

Retrieve storage zone details when an ActiveMerge workflow needs a destination checked before use.

View example

Review BunnyCDN pull zones serving ActiveMerge documents

Retrieve the BunnyCDN pull zone list on a schedule for a recurring review of document delivery zones.

View example

Verify a BunnyCDN pull zone for document delivery

Retrieve a specified pull zone's configuration and usage stats when an ActiveMerge delivery path needs a check.

View example

Refresh an entire BunnyCDN zone after a document release

Purge a specified pull zone on an agreed schedule after a batch of ActiveMerge outputs is refreshed.

View example

Review DNS records for ActiveMerge delivery domains

Retrieve DNS records on a schedule for a BunnyCDN DNS zone associated with document delivery.

Supported Triggers and Actions

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

ActiveMerge triggers

Bunnycdn actions

Recurring trigger

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

TriggerScheduled

Add Storage Zone

Creates a storage zone, an irreversible action.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Allowed Referer

ActionInstant

Create DNS Record

Creates a DNS record in a DNS zone.

ActionInstant

Add Blocked IP

Adds an IP address to a pull zone’s block list to restrict access and unwanted traffic.

ActionInstant

Create Pull Zone

Creates a CDN pull zone to cache and deliver content from your origin server.

ActionInstant

Add Blocked Referer

Adds a referer to a pull zone’s blocked list to prevent its domain from accessing content.

ActionInstant

Delete DNS Record

Deletes a specific DNS record.

ActionInstant

Delete DNS Zone

Permanently deletes a DNS zone.

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.