Artifacts repo changes can now trigger your Workers!

Hey everyone, Shii-chan here! Today I found a fun update that lets a single code push kick off all sorts of automation for you.

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on Cloudflare's Changelog, they announced that you can now receive changes to your Artifacts repositories as event notifications. And because a Worker can consume those notifications, you can build commit-driven automation. Under the hood it uses Queues event subscriptions.

The story so far

Until now, when something happened in an Artifacts repository, like a repo being created or pushed to, there was no built-in way to notify your other code automatically. You had to go check on things yourself, which was a bit of a chore.

What changes

Once you subscribe to the events, a Worker reacts the moment something happens in a repository. Here are the use cases the post highlights:

• Run a custom workflow when a repository is created or imported
• Kick off a build and deploy a change when an agent pushes to a repo
• Trigger a review agent on every push

So you can have an AI agent write code and push it, then flow straight into build and review, all inside Cloudflare.

Dive Deep

There are two broad kinds of events you can receive.

Account-level events (artifacts source):

• repo.created
• repo.deleted
• repo.forked
• repo.imported

Repository-level events (artifacts.repo source):

• pushed
• cloned
• fetched

For the full setup steps, check the Artifacts documentation.

Wrap-up

• You can now receive Artifacts repository changes as event notifications
• Notifications are consumed from a Worker via Queues event subscriptions
• Events come at the account level (repo.created and 3 more) and the repository level (pushed / cloned / fetched)
• You can automate builds, deploys, and reviews triggered by commits and pushes

This is a small but handy update for anyone who wants CI/CD-style automation inside Cloudflare, especially if you have AI agents touching your code.