Based on my understanding of Airglow, it seems an automation can only trigger in response to records being created or updated. That doesn't fit the use case I have: I'd like to use Airglow to automate a bluesky bot that posts something once a day. There might be value in a generic mechanism for creating automations that trigger on a repeating time-based schedule, like cron jobs, rather than exclusively from record updates. That would let Airglow automations drive changes to the Atmosphere rather than solely react to changes.
Something went wrong. Try again.
Automations and webhooks for the AT Protocol airglow.run
Something went wrong. Try again.