Definition
An automation inventory is a list, held in a spreadsheet or the team's documentation rather than inside the automation platform, with one row for each automated workflow that is live: nurtures, scoring, routing, stage changes, field updates, audience syncs and the flows that send email or text messages. The automation governance guide defines it and places AI agents allowed to change contact records in the same list, with their permissions written beside them.
Being outside the platform is the point. The platform's own list names each workflow and shows its status. The inventory holds what the platform cannot: the reason each one exists, the person who answers for it, what it depends on and when its purpose was last checked.
What a row records and why the gate matters
Each row answers what a reviewer would otherwise have to reconstruct from the platform's settings.
- Name and purpose. The workflow's name under the team's naming convention, and one sentence on what it does, for whom and why.
- Owner and deputy. A named person rather than a team, and who covers when they are away.
- Trigger, conditions and actions. What starts it, who is kept out, and what it does: sends, field updates, routing or an audience sync.
- Exits and priority. The conditions that end a run, and which workflows take precedence for the same contact.
- Dependencies. The fields, templates, lists, other workflows and integrations it leans on.
- Measure. The figure it is judged by and where that figure is reported.
- Status and dates. Live, paused or retired, with when it was created, last changed and last reviewed.
The governance guide makes the inventory a gate as well as a record: nothing is activated before it has a row, and a row only counts once it names an owner and a measure. The gate is what keeps the list complete. Without it, the inventory describes the platform as it stood on the day someone built the list.
In practice: governance, stage changes, closed-won flows, syncs and leavers
- Governance audits. The governance routine reads the inventory against the platform on a schedule: new workflows are checked for a row and an owner, and the full list is walked each quarter so that any workflow failing a question is fixed, given a new owner or retired.
- Stage changes. Before automating stage rules, the lifecycle stage tutorial uses the inventory to find each workflow that reads the stage, and gives every workflow it builds a row before switching it on.
- Closed-won flows. The closed-won workflow tutorial searches the inventory for workflows and sequences a contact could still be in once the deal is won.
- Syncs. The CRM sync guide keeps its field ownership table beside the inventory and treats a newly synced field as a reviewable change.
- Leavers. The tutorial on handing over a leaver's CRM records checks the inventory for workflows that refer to the departing person, then records the new owners in it.
A gym chain lists its workflows after a field rename
Jurnily Fitness, an invented gym chain with 4 clubs, renamed its membership status field in the CRM so a new booking app could read it. Three weeks later a club manager asked why lapsed members had stopped receiving the win-back offer. Three workflows checked the old field in their entry conditions: the win-back, a renewal reminder and a welcome series for members upgrading their plan. All three had enrolled nobody since the rename, and none appeared on any list the team kept. While rebuilding them, the marketing coordinator walked all 26 live workflows and gave each a row with its owner, trigger, dependencies and measure; 5 turned out to be leftovers from past campaigns and were retired. When the CRM administrator later proposed merging two payment status fields, a filter on the dependencies column showed the 4 workflows that read them before anything changed.
Related terms
A Lifecycle StageA CRM field recording where a contact stands in the relationship, such as subscriber, lead, opportunity or customer. is a field that workflows both read and write, so the dependencies column is where a change to its rules starts. Change ControlThe routine a proposed change to a live system follows: written down first, reviewed, tested, signed off and recorded before it reaches customers or data. governs edits to live workflows; the inventory is where each edit is noted against the workflow it touched, and where a reviewer finds what else depends on it. The Integration RegisterOne standing record of every connection between marketing tools: what moves, which way, keyed how, on what schedule, with whose credentials and owner. does for connections between tools what the inventory does for workflows inside one, and an audience sync can appear in both, as a workflow's action and as a connection's row. The CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. holds the fields and records workflows act on, and a renamed or merged CRM field is the kind of upstream change the inventory is there to catch. The global Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. is a shared asset that every sending workflow should check; the inventory shows which workflows send, and so which ones the check has to cover.
Common confusions
- The platform's workflow list is the inventory. It shows names and status, not purpose, owner, dependencies or when anyone last reviewed them.
- It is a content inventory. A content inventory records published pages and their review decisions; this list covers automated workflows.
- Retiring a workflow means deleting it at once. The governance guide pauses it first, amends its purpose to say why and when, and deletes it only after a defined period; the row's status shows which stage it has reached.
- AI agents need a separate register. An agent allowed to change records sits in the same list as the rule-based workflows, with what it may do written down.
