wanted it to work more realtime so i added a tenderly alert. unfortunately it couldn't wake up github actions directly, so i had to add an intermediate cloudflare worker.
but then i thought why not migrate to cloudflare worker wholesale. the architecture i ended up with is on worker that serves a static page. then tenderly could poke it using a webhook when new transactions arrive.
it indexes them into d1 sql database, and also rebuilds a json dashboard that it serves from kv to the static page as api.
i also added a daily cron as a fallback in case the webhook doesn't fire. it's all pretty simple, works well, and requires zero maintenance.
you can also scale to more complex workflows using queues. overall i found cloudflare primitives quite pleasant to work with.
for web3 webhooks the options i know are tenderly (3 alters on free plan) and alchemy (5 on free plan).
twitter.com/banteg/status/2040...
