Automations for the AT Protocol.
Airglow listens to AT Protocol events for you. Pick a lexicon, set a few conditions, and send a webhook, create a record on your PDS, or post to Bluesky.
Reviews
(1)
5.0
Como usuária de longuíssima data do IFTTT Pro+, Airglow está sendo meu playground. Simplesmente maravilhoso! Em 30 minutos ou menos consigo executar ideias completamente novas de integrações entre diferentes apps do atproto, basta entender o básico do funcionamento do protocolo, e entender bem os lexicons que deseja utilizar na automação. Ainda está bem no começo, mas já tem alguns templates bem interessantes de automações.
Updates
Partner Apps and BlueprintsAirglow is about connecting the dots in the Atmosphere. Every action you take in one app can ripple out and create value in another, so the whole network ends up worth more than the sum of its apps.
Partner Apps
The goal is to empower end users: take interoperability to the next level and help people connect their activities across the various Atmosphere apps. Getting there means working directly with app developers, building trust and powerful workflows together.
That's why we recently introduced Partner Apps. As a Partner App, you get a direct channel to your users through Blueprints, plus your own numbers on how each one is doing: how many people cloned it and how often it runs. Those numbers are for you. Airglow only ever acts on public records in the AT Protocol, so there's no hidden tracking going on.
App accounts like @bookhive.buzz, @kipclip.com and @sifa.id sign up on Airglow and we flag them as partners. It's a manual step on our side for now, but once the community app lexicons give us a clean list of app accounts, we'll make it automatic. And there's no lock-in: Airglow is open source and easy to self-host, so nothing you build here is stuck with us.
Blueprints
Blueprints are automation templates meant to be duplicated. They show up in the gallery under your app's name and logo, ready for any of your users to clone to their own account in one click.
A few partners have already published theirs. Bookhive posts to Bluesky when you finish a book. Kipclip bookmarks and annotates the links from any Bluesky post you like. Sifa posts to Bluesky when someone endorses you. One action in their app, more value somewhere else in the network, none of it built or maintained by them.
That last part is the point. When you publish a Blueprint, you're telling your users this automation is safe, it works, and you stand behind it. It's an endorsement they can act on with a single click, and you never touch the plumbing. Publishing one is simple: build the automation, tick "Mark as Blueprint", and it lands in the gallery under your name.
Conclusion
In a nutshell, Airglow now has a solid technical foundation. The focus for the next few weeks and months is to explore more complex use cases and work with app maintainers to figure out how we can serve their users best.
Alongside that, we want Airglow to look and feel more professional, so we're working with a brand designer to fully revamp the Airglow brand and voice. It should be ready to unveil in the first half of June, and at the same time we'll ship the new Blueprints gallery.
Our goal is clear: we want Airglow to be featured on tools like Eurosky and at-store, not as a regular app, but as a meta-app. A piece of infrastructure in the Atmosphere that people and app developers can rely on to build complex workflows.
We're already onboarding Partner Apps, so if you want in, reach out to @there-hugo.dev or @airglow.run on Bluesky.
May 25, 2026
Sharing or not sharing social graph, why not both?Airglow now has a "Follow" action. You can build automations like "when I follow someone on Bluesky, follow them on Sifa", and keep your follows in sync across the apps you use.
Here is why we built it, how it works, and how to set it up.
The debate, briefly
Many social apps on the Atmosphere have their own social graph. Bluesky has one. So do @sifa.id, @tangled.org, @semble.so, and more. The fact that these apps built their own follow lexicons rather than reusing Bluesky's is itself an answer to the question: their developers reckoned that not every user wants to follow the same people on their platform as they do on Bluesky. Different app, different context, different graph.
Sifa still helps you find your people without forcing the graphs to be the same. On the homepage you'll see "N new people you follow on Bluesky or Tangled are on Sifa. Show me who", and you decide one by one. The graph stays Sifa's own, the discovery uses your other graphs as a hint.
With Airglow, we're addressing the other side: for users who do want the same graph across apps, you can now keep your follows in sync automatically, with rules you choose, on the pairs of apps you choose.
When syncing makes sense
For my own use case, Bluesky, Tangled, and Sifa are all work and dev related, so it makes sense for me to keep those graphs in sync. Someone with a more split identity might want Bluesky and Sifa synced but leave Grain alone for personal stuff. The point is that this is a per-pair decision, made by the user.
How it works
You set up two automations per app you pair with Bluesky:
- When I follow someone on Bluesky, follow them on Sifa
- When I follow someone on Sifa, follow them on Bluesky
Same pattern for Tangled, Semble, and any other app. Bluesky becomes the hub by virtue of being the only app every other one is paired with.
The cascade falls out for free. Follow someone on Sifa, the Sifa-to-Bluesky automation fires and creates the Bluesky follow, that Bluesky follow fires the Bluesky-to-Tangled and Bluesky-to-Semble automations, records appear on Tangled and Semble. One follow, four apps, no manual work.
The cascade terminates because of an existing-follow check at every step. Before the action creates a new follow record, it verifies you don't already follow that person on the destination app. So when the Bluesky follow comes back around to fire the Bluesky-to-Sifa automation, it sees you already follow them on Sifa and stops. No loops.
This check is also what keeps the setup small as you add apps. Adding a fifth app to your sync means two new automations, not eight, because you only pair it with Bluesky and let the cascade do the rest.
Pro-tip: you can even have only one automation to handle the follow from Bluesky to Sifa, Tangled, Semble.
Setting it up
Browse the existing follow automations and duplicate/customize what you want. Each automation duplicates to your account in one click.
For most people the practical recipe is: pair Bluesky with each other app you use, in both directions. That covers the bidirectional sync and gives you the cascade automatically.
Implementation notes
The Follow action is a more specific, smarter version of the generic "Create record" action. Before creating a new follow, it checks two things:
- the target user has a profile on the destination app
- you don't already follow them there
The second check is the one that makes the cascade safe. It's also the one that's interesting to implement. On Bluesky, app.bsky.graph.getRelationships makes the check trivial. Most other apps don't have an equivalent endpoint yet, so we fetch the user's follow records from their PDS and scan. If you follow a couple hundred people, that's fine. If you follow a couple thousand, that's twenty pages of a hundred records each.
Workable for now. As the per-app graphs grow, more apps will probably want their own appview with a getRelationships equivalent. That's a question for the app developers, not for us.
What's next
The opposite action, automated unfollows, is in the works.
Beyond that, the Follow action is one specific case of a more general pattern: user-defined rules that move records between lexicons on your own PDS. Other things you can build with the existing primitives include automated follow-back, greeting new followers, or following anyone who performs a specific action on a specific app.
Try it out at Airglow.run. If there's an app you'd like us to integrate next in the Follow action, let us know.
Apr 25, 2026
Automatically announce blog posts on BlueskyThe perfect use case
Let's say you just published a new blog post on @offprint.app, @leaflet.pub, @pckt.blog, or your own blog that uses @standard.site. You may want to post something on Bluesky to announce it.
Airglow lets you build this exact workflow. Especially thanks to a few features that were released today:
- Automatically resolve links (and other facets) in Bluesky posts
- Retrieve data from previous actions, such as the ID of a new Bluesky post
- Update records on your PDS, to link the blog post back to its Bluesky announcement
How to implement it
You can sign in on Airglow with the account you use to post, and duplicate this action:
It will be enabled on your account and run in "dry-mode" by default, meaning that it won't actually perform the actions. You can disable "dry-mode" straight away, and your next blog entry will automatically be posted on Bluesky.
How it works
This automation subscribes to the creation of site.standard.document records. It then filters publications that belong to your DID.
It fetches the original publication based on {{event.commit.record.site}}, to retrieve the base URL of the blog.
It then performs two actions:
- A "Bluesky post" action, that creates the Bluesky post with the title {{event.commit.record.title}} and the URL, built from the publication record {{publication.record.url}}{{event.commit.record.path}}.
- Update the original site.standard.document that triggered the event to set the bskyPostRef, so that the blog post is linked to the Bluesky post.
Next steps
You'll see your action logs on https://airglow.run every time it runs, it's especially useful if an error happens.
And you can set up many more automations on Airglow, even just call arbitrary HTTP callbacks. It really enables a lot of use cases.
Apr 13, 2026Mentions
@airglow.run @semble.so I'm not sure anymore if that might be an Airglow or Semble problem... Or even both... So I have an automation that fetches the stars I give on Tangled repositories, builds the Tangled URL for that repository (permalink), creates a Semble... View full post
5/19/26, 2:35 PM
Pssst: Duplicate this automation to automatically RSVP to future sessions airglow.run/u/there-hugo...
RSVP to Off Protocol sessions | @there-hugo.dev | Airglow
When @atproto.com (AT Protocol Developers) creates an Off Protocol event, RSVP as interested
https://airglow.run/u/there-hugo.dev/3mm4kem6dks22
5/18/26, 9:22 AM
Am I doing this right? airglow.run/u/bookhive.b... It’s unclear to me whether this is setting up an automation for my bookhive account or if this is making a template for others to use
Post on Bluesky when I finish a book | @bookhive.buzz | Airglow
When I mark a book as finished on Bookhive, write a post on Bluesky
https://airglow.run/u/bookhive.buzz/3mlygkr3d6c22
5/16/26, 6:04 PM
