Operator
← All integrations
Bunnycdn logo+GitHub logo

Connect Bunnycdn to GitHub

Automate Bunnycdn and GitHub with AI

Every GitHub deploy to production should purge the CDN cache that still serves stale assets. On Operator.io, an OpenClaw agent ties BunnyCDN to your repo so merges to the branch you name trigger a purge for the paths that changed, and failed purges open a GitHub issue with the API response attached. Roll back from chat and it purges again after the revert commit lands.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Bunnycdn and GitHub

What your agent does in Bunnycdn

  • Add Allowed Referer

    Adds a hostname to the allowed referer list for a pull zone. Use this action to restrict content access by configuring referer-based security. Only requests with a Referer header matching one of the allowed hostnames will be able to acce...

  • Add Blocked IP

    Tool to add an IP address to the blocked list of a pull zone. Use when you need to restrict access from specific IPs to prevent unwanted traffic.

  • Add Blocked Referer

    Tool to add a blocked referer to a pull zone. Use when you need to prevent specific domains from hotlinking or accessing content from your CDN.

  • Add Storage Zone

    Tool to add a new storage zone. Use when you need dedicated file storage in a specific region. Zone creation is irreversible — confirm Name, Region, and ZoneTier before executing.

  • Add/Update Edge Rule

    Tool to add or update edge rules in a BunnyCDN pull zone for advanced traffic control. Edge rules allow conditional request processing based on triggers like URL patterns, headers, country codes, or IP addresses. Each rule can perform ac...

  • Check DNS Zone Availability

    Tool to check if a DNS zone name is available for registration. Use before creating a new DNS zone to verify the domain name is not already in use.

All 126 Bunnycdn actions →

What your agent does in GitHub

  • Abort Repository Migration

    Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.

  • Accept a repository invitation

    Accepts a PENDING repository invitation that has been issued to the authenticated user.

  • Add app access restrictions

    Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...

  • Add a repository collaborator

    Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...

  • Add assignees to an issue

    Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.

  • Add email for auth user

    Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...

All 846 GitHub actions →

How it works

Tell the agent what you want to happen between Bunnycdn and GitHub, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Bunnycdn, works out what to do, and runs the matching action in GitHub without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Bunnycdn and GitHub

How do I connect Bunnycdn and GitHub to Operator?
You authorize Bunnycdn and GitHub once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Bunnycdn and GitHub?
You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Bunnycdn and GitHub actions on its own, so you do not map fields or pick triggers.
Can my agent keep Bunnycdn and GitHub in sync?
Yes. It can watch Bunnycdn and act in GitHub, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Bunnycdn and GitHub integrations

Put your agent on Bunnycdn and GitHub

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free