Hi Seth,
This is what I am making now: a program (or existing Jenkins plugin) which reads new email, processes it and moves it to deleted items. The Jenkins job calls this program and hooks into the process part to do whatever we have to do - including separating mails by envs since ops is not really interested in non prod publishes, publishing Tealium publish history to the wiki etc.
While it should work, from a user point of view it is much better to have access to an API for automation like this.
More about why we are adding this process:
In our case, Tealium pixel publishes happen outside the normal release cycle and often dont go through the same test/validation cycle other code does. Recently we have had some issues where we want ops to have better visibility into Tealium publications while triaging prodution issues. Tealium JavaScript is loaded late asynchronously, but issues in the code could (and has) caused issues with other late loading JavaScript. This includes SiteCatalyst which while loaded via Tealium needs a 100% uptime. This is not a Tealium issue per se, more to do with how we release pixel code out-of-band with less QA.
Thanks,
Sriram