Own the workflow. See what happens.
Replacing hosted automation steps with coded workflows that the team can maintain and inspect.
The problem.
Operational workflows cross systems: an event registration needs downstream updates, a certificate needs to be generated, or a new feed item needs to reach the right place. The team needs to understand what happened and maintain the behavior over time.
What I built.
I worked on moving these tasks into maintained code, including order handling and downstream updates, certificate automation, and feed processing. The work connects independent steps with explicit processing and operational visibility.
The decisions that matter.
Make the steps explicit
Keep downstream work understandable and separately inspectable.
Handle repeated delivery deliberately
Design event processing so that a repeated input can be recognized and handled.
Treat operation as part of the build
Include status and maintenance workflows alongside the automated action.
The result.
By 19 October 2026, 18 hosted automations had been retired. The replacement work spans event registration, publishing, certificates, and staff feed workflows.
Built with.
- Clojure
- Webhooks
- Scheduled jobs
- API integration