The three alerts every automation needs before it reaches a client
An automation builder never ships a workflow that can fail silently to a non-technical client. Three alerts go on every handoff: one for runs that produce zero or suspiciously few results, one for errors that stop the run (routed to the builder with context, not to the client), and one warning days ahead when a credential or token is about to expire. Clients do not need the automation to be perfect; they need to know the instant it is not, and to know the builder saw it first.