How I automate DEV recipe cleanup in Workato
Hello Folks, Sharing a quick governance automation for folks newer to Workato (though I’m sure many seasoned builders here have built something similar!). The Problem: How often do we build a recipe in DEV, test it, deploy it to PROD… and completely forget to turn off the DEV version? Scheduled recipes in particular can sit in DEV silently burning through tasks for weeks without anyone noticing. The Solution: Automated DEV Recipe Stopper I built an automated governance flow to keep DEV task consumption under control without getting in the way of active development. Here’s how it works: 1. 7-Day Check-In: Once a recipe has been running in DEV for 7 days, the automation stops it and sends you a Slack notification with quick usage stats. 2. Interactive Options: Right inside Slack, you get three simple buttons: 🔄 Restart: Turns the recipe back on and resets the 7-day timer. 📅 Stop After: Lets you pick a tentative date if you know your testing needs a few more days. 🛑 Never Stop: Pops up a quick modal asking for a justification (which logs directly into a Workato Data Table for audit/governance). The Impact: Since rolling this out, the drop in unnecessary DEV task consumption has been huge—the graph below pretty much tells the whole story! Curious how other teams handle DEV cleanup or task governance—do you run something automated like this, or rely on manual audits?
