Name the outcome, not the bot colour
When a release renames a workflow step, every success report keyed on the old label goes quiet—or worse, stays loud with the wrong meaning.
Teams often treat automation event names as disposable labels. A designer renames a approval step, an engineer ships a new retry path, and suddenly step_complete and case_closed both exist for different moments. Reports that once looked clean become archaeological digs.
Prefer verbs that describe the business outcome—invoice_reconciled, ticket_resolved_without_human, shipment_label_issued. Keep platform names out of the event; put them in a property so RPA, iPaaS, and native app automations stay comparable. Write allowed properties on the same day you create the event.
In Automation Success Baseline engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.