Mattering Automations bunny.net integration
Connect bunny.net to Mattering Automations: pull zones with custom hostnames, Force SSL, and edge rules, cache purge by zone, tag, or URL, Bunny DNS zones and records with BIND export, storage zone management, CDN and DNS and storage statistics, and billing reads as workflow steps, authenticated with one account API key.
The Mattering Automations bunny.net integration adds the bunny.net core API to your automation canvas: list and manage CDN pull zones from creation through custom hostnames, Force SSL, and edge rules, purge the cache by zone, by cache tag, or by URL with wildcard support, manage Bunny DNS zones and records with BIND zone-file export, create and configure storage zones, read CDN, DNS, and storage statistics over any date window, and read billing details and per-zone usage summaries.
The credential is the bunny.net account API key, found in the bunny.net dashboard under Account, then API Key, and sent as an AccessKey header on every request. Every bunny.net account has one, including trial accounts, and it carries full access to the account. It is a different credential from storage zone passwords and Bunny Stream library keys, which authenticate bunny.net's separate file and video APIs; this integration stores only the account key, and file and video operations are deliberately out of its scope. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.
The safety modeling is stated on the nodes rather than buried. Of the 38 nodes, 18 read and 20 act, and five carry a destructive flag: bunny.net: Delete Pull Zone, bunny.net: Delete Storage Zone, bunny.net: Delete DNS Zone, bunny.net: Delete DNS Record, and bunny.net: Delete Edge Rule. The storage zone delete is the one to respect most: it removes every file stored in the zone, unrecoverably, and by default also deletes pull zones linked to it. bunny.net's API also embeds storage passwords and Stream keys inside storage zone and video library responses, so the nodes returning those objects warn about it in their descriptions.
Before you start
- A bunny.net account with an active trial or a positive balance. bunny.net gives new accounts a 14 day trial with trial credits and runs prepaid, pay as you go after that; there is no permanent free tier, but the API itself costs nothing beyond the resources it manages, and a trial account can exercise every node family.
- Access to the account API key in the bunny.net dashboard. The key carries full access to the account, so if your team separates duties, the person connecting bunny.net to Mattering should be one who is allowed to hold that key.
- At least one pull zone or DNS zone to point the first workflows at. Both can be created by the integration itself (bunny.net: Create Pull Zone, bunny.net: Create DNS Zone), so an empty account is fine too; the verify section below reads cleanly either way.
- A Mattering workspace with access to the Automations app.
- Not required and not stored here: storage zone passwords and Bunny Stream library keys. Those authenticate bunny.net's separate file and video APIs on other hosts, which this integration does not cover.
Get your bunny.net account API key
Mattering authenticates to bunny.net with the account API key, sent as an AccessKey header on every request to api.bunny.net. bunny.net has one such key per account, created for you when the account is made, so there is nothing to generate and no scopes to choose: the key simply is the account's API identity. That cuts both ways. Setup is short, but the key has full access to everything the account owns, so treat it like a root credential and store it only in systems built to hold secrets.
Connect bunny.net to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a bunny.net section should list the query and action nodes. Drop bunny.net: List Pull Zones onto the canvas and run a test step. It is the integration's natural probe: every account key can call it, it takes no required parameters, and by default bunny.net returns every zone as a plain array, so the IDs sit at data[].Id. Copy a pull zone ID, because the zone nodes, the purge node, and the statistics filter all ask for it.
Next, run bunny.net: List DNS Zones and note the different shape: DNS listers return an Items envelope, so the zone IDs sit at data.Items[].Id, and every DNS node needs one. If you use bunny.net storage, bunny.net: List Storage Zones completes the picture, with one caution: bunny.net includes each zone's storage passwords in that response by design, the node description calls this out, so treat the output like the credential it contains. Everything in this verify path is read-only: it cannot reach the five destructive nodes or change a single setting, so it is safe to re-run whenever you rotate the key.
Node reference
38 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 18
bunny.net: Export DNS Zone
bunny_export_dns_zone
Export a DNS zone as a BIND zone file (plain text). Use it as a backup before destructive changes or to migrate records to another provider.
bunny.net: Get Billing Details
bunny_get_billing_details
Current billing state of the account: balance, this month's charges broken down by product and traffic region, monthly bandwidth used, and recent billing records. A point-in-time gauge of the account, not a windowed report.
bunny.net: Get Billing Summary
bunny_get_billing_summary
Per pull zone usage summary for the current month: each zone's monthly usage amount and bandwidth used, as a plain array. A point-in-time gauge, not a windowed report.
bunny.net: Get Country List
bunny_list_countries
List countries as bunny.net knows them: name, ISO code, EU membership, and tax metadata. The ISO codes are the values used in pull zone country block lists (BlockedCountries via Extra body fields on the update node).
bunny.net: Get DNS Query Statistics
bunny_get_dns_statistics
DNS query statistics for a zone over a date window: total queries served for the whole window plus charts keyed by timestamp (QueriesServedChart, NormalQueriesServedChart, SmartQueriesServedChart) and a breakdown keyed by record type (QueriesByTypeChart). Defaults to the last 30 days when no window is set.
bunny.net: Get DNS Zone
bunny_get_dns_zone
Fetch one DNS zone with its full record list, nameserver configuration, SOA email, and DNSSEC status.
bunny.net: Get Pull Zone
bunny_get_pull_zone
Fetch one pull zone: origin, hostnames, cache and security settings, geo zones, and its edge rules (each with the Guid used by the edge rule nodes, at data.EdgeRules[].Guid).
bunny.net: Get Statistics
bunny_get_statistics
CDN traffic statistics over a date window, account-wide or filtered to one pull zone or region: whole-window totals (bandwidth, requests, cache hit rate, origin response time) plus charts keyed by timestamp (BandwidthUsedChart, RequestsServedChart, CacheHitRateChart, and more) and a geographic traffic breakdown. Defaults to the last 30 days when no window is set.
bunny.net: Get Storage Zone
bunny_get_storage_zone
Fetch one storage zone: name, main and replication regions, files stored, storage used, and its passwords for the separate storage file API (treat as sensitive).
bunny.net: Get Storage Zone Regions
bunny_list_storage_regions
List the available storage regions with their codes (used as the Region and replication values when creating a storage zone), names, and storage hostnames.
bunny.net: Get Storage Zone Statistics
bunny_get_storage_zone_statistics
Storage usage over a date window: bytes stored and file count as charts keyed by timestamp (StorageUsedChart, FileCountChart). Both series are point-in-time gauges of the zone's size, not per-day flows; never sum them across days. Defaults to the last 30 days when no window is set.
bunny.net: Get Video Library
bunny_get_video_library
Fetch one video library: player and encoding configuration, linked pull zone and storage zone, and its Stream API keys (treat as sensitive).
bunny.net: List DNS Zone Records
bunny_list_dns_records
List a DNS zone's records as a paginated Items envelope: record IDs, integer type codes, names, values, and TTLs. The record ID from here feeds the update and delete nodes.
bunny.net: List DNS Zones
bunny_list_dns_zones
List the account's DNS zones as a paginated Items envelope: zone IDs, domains, nameserver status, and logging settings. The zone ID from here feeds every DNS node.
bunny.net: List Pull Zones
bunny_list_pull_zones
List the account's CDN pull zones with their numeric IDs, names, origin URLs, hostnames, and edge rules. By default (page blank) bunny.net returns every zone as a plain array; set page to 1 or higher for a paginated Items object. The pull zone ID from here feeds every pull zone node and the statistics filter.
bunny.net: List Storage Zones
bunny_list_storage_zones
List the account's storage zones with IDs, names, regions, usage, and connected pull zones. By default (page blank) bunny.net returns every zone as a plain array. The response includes each zone's storage passwords (that is how the separate storage file API authenticates), so treat the output as sensitive.
bunny.net: List Video Libraries
bunny_list_video_libraries
List the account's Bunny Stream video libraries: IDs, names, video counts, and storage usage. Returns a plain array by default; set page to 1 or higher for a paginated Items envelope instead. The response includes each library's Stream API keys by design of the vendor API, so treat the output as sensitive. Video upload and management happen on the separate Stream API host, out of scope for this connector.
bunny.net: Region List
bunny_list_regions
List the bunny.net CDN regions with their numeric IDs (used by the statistics region filter), region codes, names, and coordinates.
Action nodes 20
bunny.net: Add DNS Record
bunny_add_dns_record
Add a record to a DNS zone (a PUT request per the vendor spec). Returns the created record including its ID. Reversible with bunny.net: Delete DNS Record.
bunny.net: Add Pull Zone Hostname
bunny_add_pull_zone_hostname
Attach a custom hostname (for example cdn.example.com) to a pull zone. Point the hostname's DNS at the zone's b-cdn.net hostname with a CNAME, then issue SSL separately. Returns 204 with no body. Reversible with bunny.net: Remove Pull Zone Hostname.
bunny.net: Add or Update Edge Rule
bunny_add_or_update_edge_rule
Create an edge rule on a pull zone, or update an existing one when its Guid is supplied. An edge rule pairs an action (redirect, header change, cache override, block) with URL or header triggers. Returns 201 with no body; read the resulting rules (and their Guids) with bunny.net: Get Pull Zone at data.EdgeRules[].
bunny.net: Create DNS Zone
bunny_create_dns_zone
Add a domain to Bunny DNS. The zone is served by the bunny.net nameservers once the domain's registrar points at them. The vendor spec documents the 201 response without a body, so follow with List DNS Zones to read the new zone's ID. Reversible with bunny.net: Delete DNS Zone.
bunny.net: Create Pull Zone
bunny_create_pull_zone
Create a CDN pull zone from a URL origin or a bunny.net storage zone. Name becomes the default hostname name.b-cdn.net. The vendor spec documents the 201 response without a body, so follow with List Pull Zones or Get Pull Zone to read the new zone's ID. Reversible with bunny.net: Delete Pull Zone. The full 146-field creation model (cache, security, Optimizer, logging) is reachable via Extra body fields.
bunny.net: Create Storage Zone
bunny_create_storage_zone
Create an edge storage zone. Returns the created zone including its ID and the passwords used by the separate storage file API. Replication regions cannot be removed later, only added. Reversible with bunny.net: Delete Storage Zone.
bunny.net: Delete DNS Record
bunny_delete_dns_record
DESTRUCTIVE: delete a DNS record. Whatever the record pointed at stops resolving; the record must be re-created to restore it (disable it instead if it might come back). Returns 204 with no body.
bunny.net: Delete DNS Zone
bunny_delete_dns_zone
DESTRUCTIVE: delete a DNS zone and every record in it. The domain stops resolving through Bunny DNS immediately and the records cannot be restored; export the zone first with bunny.net: Export DNS Zone if there is any doubt. Returns 204 with no body.
bunny.net: Delete Edge Rule
bunny_delete_edge_rule
DESTRUCTIVE: delete an edge rule from a pull zone. The rule's triggers and action configuration are removed and must be re-authored to restore; disable the rule instead if it might come back. Returns 204 with no body.
bunny.net: Delete Pull Zone
bunny_delete_pull_zone
DESTRUCTIVE: delete a pull zone. Its hostnames, edge rules, and configuration are removed and content stops being served through the zone immediately; the configuration cannot be restored. Returns 204 with no body.
bunny.net: Delete Storage Zone
bunny_delete_storage_zone
DESTRUCTIVE: delete a storage zone AND every file stored in it, unrecoverably. By default bunny.net also deletes pull zones linked to the storage zone. Returns 204 with no body.
bunny.net: Purge Pull Zone Cache
bunny_purge_pull_zone_cache
Purge a pull zone's entire cache, or only objects carrying a specific cache tag when CacheTag is set. Content is re-fetched from the origin on the next request; nothing is deleted at the origin, so this is safe but does raise origin traffic until the cache refills. Returns 204 with no body.
bunny.net: Purge URL
bunny_purge_url
Purge a single URL from the CDN cache without knowing which pull zone serves it. Wildcards purge path families, for example https://example.b-cdn.net/assets/*. The next request re-fetches from the origin; nothing is deleted at the origin. Returns 200 with no body.
bunny.net: Remove Pull Zone Hostname
bunny_remove_pull_zone_hostname
Detach a custom hostname from a pull zone (a DELETE request that carries a JSON body). The hostname stops serving through the zone; re-adding it reverses the change. Returns 204 with no body.
bunny.net: Set Edge Rule Enabled
bunny_set_edge_rule_enabled
Enable or disable one edge rule without editing it. Returns 204 with no body. Reversible by setting the opposite value.
bunny.net: Set Force SSL
bunny_set_force_ssl
Turn Force SSL on or off for one hostname on a pull zone (redirects HTTP requests to HTTPS when on). Returns 204 with no body. Reversible by setting the opposite value.
bunny.net: Update DNS Record
bunny_update_dns_record
Update a DNS record. The vendor's update model carries the same fields as record creation, so send the record's intended state (read it first from bunny.net: List DNS Zone Records) rather than a single changed field. Returns 204 with no body.
bunny.net: Update DNS Zone
bunny_update_dns_zone
Update a DNS zone's settings: custom nameservers, SOA email, and query logging. Only fields you fill are sent. Returns the updated zone. Reversible by writing the previous values back.
bunny.net: Update Pull Zone
bunny_update_pull_zone
Update a pull zone's configuration (bunny.net updates use POST, not PATCH). Only fields you fill are sent; the rest of the 145-field settings model (geo zones, security, Optimizer, rate limits) is reachable via Extra body fields. Returns the updated zone. Reversible by writing the previous values back; read them first with bunny.net: Get Pull Zone.
bunny.net: Update Storage Zone
bunny_update_storage_zone
Update a storage zone's settings: add replication zones, set a fallback origin URL, a custom 404 file path, or rewrite 404s to 200. Only fields you fill are sent. Returns 204 with no body.
Using the integration
On the automation canvas
bunny.net nodes chain with every other node: a deploy webhook can run bunny.net: Purge Pull Zone Cache with a cache tag and then open a verification task in Mattering Productivity, a scheduled sweep can read bunny.net: Get Statistics across the account and write bandwidth and cache hit rate into a Mattering database, and bunny.net: List DNS Zone Records can feed a domain inventory that lives next to the rest of the work. The pull zone ID from bunny.net: List Pull Zones and the DNS zone ID from bunny.net: List DNS Zones are the two values almost every downstream node asks for.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can read a zone with bunny.net: List DNS Zone Records, take a one-node backup with bunny.net: Export DNS Zone, repoint a record with bunny.net: Update DNS Record, and clear the right cache with bunny.net: Purge URL. The read nodes are the safest surface to hand an agent; keep the five destructive nodes behind conditions or approval steps.
DNS with the export step built in
bunny.net: Export DNS Zone returns the zone's complete record set as BIND zone-file text, and running it before any bulk change is the habit that makes DNS automation calm: it is a backup you can carry into an approval task or replay at another provider. One vendor behavior shapes the write side: bunny.net's record update carries the same fields as record creation, so bunny.net: Update DNS Record sends the record's full intended state rather than one changed field. Read the record first with bunny.net: List DNS Zone Records, change what you mean to change, and send the whole record back. bunny.net: Add DNS Record returns the created record with its ID, and the destructive-flagged bunny.net: Delete DNS Record belongs behind a gate.
Cache purge with the right blast radius
Two nodes, two scopes. bunny.net: Purge Pull Zone Cache flushes a zone's whole cache, or only the objects carrying a specific cache tag when CacheTag is set. bunny.net: Purge URL clears one URL without knowing which zone serves it, and wildcards purge path families, for example https://example.b-cdn.net/assets/*. Neither deletes anything at the origin; purged content is simply re-fetched on the next request, which is also the honest caveat: a full-zone purge on a busy site sends the origin a cold-cache refill, so prefer tags and wildcard prefixes when only part of the site changed.
Edge rules, including the no-lister quirk
bunny.net: Add or Update Edge Rule writes rules that pair an action (redirect, header change, cache override, block) with URL or header triggers, and bunny.net: Set Edge Rule Enabled flips a rule on or off without editing it, which turns a prepared maintenance redirect or block rule into a switch a workflow can throw and later throw back. The quirk to know: bunny.net has no endpoint that lists edge rules on their own. Rule Guids live inside the zone detail from bunny.net: Get Pull Zone at data.EdgeRules[].Guid, so the pattern is get the zone, find the rule, then act on its Guid. bunny.net: Delete Edge Rule is flagged destructive because a removed rule's triggers and configuration must be re-authored; disable instead when the rule might come back.
The five destructive nodes, gated
bunny.net: Delete Storage Zone is the heaviest: it removes the zone and every file stored in it, unrecoverably, and by default bunny.net also deletes pull zones linked to that storage zone, so one call can take down both the storage and the CDN serving it. bunny.net: Delete DNS Zone stops the domain resolving through Bunny DNS immediately and takes every record with it, so run bunny.net: Export DNS Zone first if there is any doubt. bunny.net: Delete Pull Zone stops content serving through the zone and discards its hostnames, edge rules, and configuration. The remaining two (bunny.net: Delete DNS Record, bunny.net: Delete Edge Rule) are smaller but equally final. The pattern for all five is the same: read or export the thing first, and put the delete behind a condition, an approval task, or a manual run rather than a bare trigger.
What stays off the canvas
Three boundaries are deliberate, and all three come from bunny.net's own architecture. Files inside storage zones: upload, download, list, and delete run on bunny.net's storage API, separate per-region hosts authenticated with per-zone passwords rather than the account key, so this integration manages the zones (bunny.net: Create Storage Zone, bunny.net: Update Storage Zone, bunny.net: Get Storage Zone Statistics) and leaves the files to the tools holding those keys. Videos in Bunny Stream: upload and management live on the Stream host with per-library keys, so the integration reads libraries with bunny.net: List Video Libraries and bunny.net: Get Video Library and stops there. And bunny.net's separate product APIs, such as Shield and Edge Scripting, are their own surfaces and are not part of this integration.
Troubleshooting
Test Connection fails with a 401 error
Every node suddenly returns 401 after working fine
A create node succeeds but returns no object
List Pull Zones returns a plain array instead of pages
Update DNS Record blanked fields I did not touch
The edge rule nodes want a Guid I cannot find a lister for
Origin traffic spikes right after a purge
Storage statistics do not add up when summed across days
Related
The bunny.net MCP
What connecting bunny.net unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
bunny.net is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.