Automator Library manages the curated automators and email templates teams can browse and install from their own Automators page — three tabs: Automators, Email Templates, and Install failures.
Automators tab
Use the New automator button (top-right of the page) to start one from scratch — name it, set its Slug (auto-filled from the name, editable — this can't be changed later, so get it right here), and pick a Home stage, then it opens straight into the step-list editor to build out. The same button appears in the empty state before any templates exist yet.
Select a row (anywhere outside its Auto-install switch or row menu) to open its step-list editor — the same builder used for a team's own automators (see Building an automator) with a few library-specific fields in the header: an Auto-install toggle, a Home stage picker, and a version badge. Back on the list, each row shows its Stage, Trigger, Version, and Status (Draft, Published, or Archived), and its Auto-install switch is editable inline. Open the row's ⋯ menu for Publish (or Republish, once already published) and to Move up / Move down its position in the list.
Email Templates tab
Use the New email template button (top-right of the page) to start one from scratch — name it, set its Slug (auto-filled from the name, editable — this can't be changed later, so get it right here), and pick a Category, then it opens straight into the inline editor with a blank subject and body to fill in. The same button appears in the empty state before any templates exist yet.
Select a row to open its inline editor — subject, body, category, Active, and Auto-install, plus a merge-field insert menu. Back on the list, Active and Auto-install are editable inline per row, and Publish is a button on the row.
Publishing
Publishing (from either tab) opens a confirm dialog showing exactly how many installed team copies will auto-update and how many customized copies will instead get an update offer, before you commit. If you publish an automator with no triggers staged at all, TED automatically adds an enabled Manual start trigger first — a one-time note confirms this — so the template never installs into a team as an automator nothing can start. Remove that trigger and publish with truly zero triggers staged, and the trigger list's empty state reads "Teams that install this can't start it until they add one."
Install failures tab
A per-team template install, republish, or manual install can occasionally hit a genuine error (not the resolvable-slug case, which lands a team's copy as a draft with its own on-page warning banner — that's already visible to the team). The Install failures tab lists every one of those, most recent first: which team, which template, when it happened (new team, republish, or manual install), and the error itself. A red count badge on this tab and on the Automator Library entry in the sidebar shows how many are still unacknowledged.
Click Acknowledge on a row once you've looked into it — the row drops off the list. Team creation, republishing, and manual installs are never blocked by one of these errors; this tab exists purely so a real failure doesn't go unnoticed. If the tab is empty, every install is clean.