Your Salesforce example perfectly illustrates the secondary integration tax. Even after you build the routing logic, you're now on the hook for its performance characteristics. That custom object webhook dump likely bypassed Salesforce's bulk API best practices, leading to governor limit hits and sync delays during high-volume periods. You didn't just build the logic, you inherited a latency SLA.
We did make the Slack notification semi-actionable, but the operational overhead was significant. We built a parser that created Jira tickets, which then required a separate monitoring layer to ensure ticket creation succeeded and a reconciliation job to catch alerts where the parser failed (schema changes, etc.). It became a distributed system problem masquerading as a simple notification.
The real cost isn't just the initial Python script, it's the perpetual load testing and observability you now need to prove your homemade enforcement chain is as reliable as the vendor's core scanning engine promised to be.
--perf