Skip to content

Automation inventory · v0.1 preview

What your automation layer has quietly accumulated.

Midden inventories every workflow across Zapier, Make, n8n, Power Automate, and Workato. It surfaces orphaned automations, silent failures, and connections to services that no longer exist.

The problem

Every team inherits automations they did not build and cannot find.

01 / ACCUMULATION

Accumulation without deletion

Teams add workflows every month. Almost nobody retires them. The layer only grows, and the map gets harder to draw. What was a clean catalog two years ago is now a shelf nobody wants to open.

02 / DRIFT

Ownership drifts

A workflow runs every night. The person who built it left eighteen months ago. Nobody has opened it since, and nobody wants to be the one who asks whether it still matters.

03 / SILENCE

Silent failure

A scheduled job runs on time, posts nothing downstream, and nobody notices until a monthly report arrives with missing numbers. By then the chain has been quiet for a quarter.

What Midden surfaces

Six platforms. Six questions. One inventory per workspace.

Zapier
last success · step errors · owner tenure
last produced output 94 days ago
Make
scenario state · webhook endpoint health
depends on endpoint retired Q2 2023
n8n
credential owner · cron fidelity
owner no longer employed · 412 runs since
Power Automate
connection status · flow triggers
triggered by deprecated Dataverse entity
Workato
recipe state · connector version
connector EOL 11 months ago
Cross-platform
duplicate logic · overlapping schedules
two workflows write the same sheet

Stratigraphy

A core sample of the workflows your team has laid down, quarter by quarter.

Each band is a quarter. Each cell is one workflow added in that period. Flagged entries sit in sepia.

Automation stratigraphy Six horizontal time bands from Q2 2026 at the top to Q1 2025 at the bottom. Sepia cells mark flagged workflows. Q2 2026 22 added · 2 flagged Q1 2026 18 added · 1 flagged Q4 2025 29 added · 4 flagged Q3 2025 15 added · 2 flagged Q2 2025 31 added · 5 flagged Q1 2025 26 added · 3 flagged

inventory / revops · workspace: growth · 141 workflows

17 flagged · 124 active

How it works

Four steps from connection to inherited clarity.

  1. 01

    Connect

    Read-only OAuth to each platform. Midden never runs, schedules, or modifies a workflow.
  2. 02

    Inventory

    Every workflow catalogued with its last run, last change, estimated owner, and the downstream surface it touches.
  3. 03

    Analyze

    Signatures of orphan, silent failure, and deprecated connection applied. Findings are grouped and dated.
  4. 04

    Report

    Findings returned to you with context. You decide what to keep, archive, or rewrite.

Trust

What we touch. What we retain. What we cannot do.

Read-only, always
We do not execute, schedule, or modify any workflow. Nothing runs because of Midden.
Metadata over payload
We analyze schedule, owner, endpoints, and last status. Payload contents are not retained.
Your region, your data
Findings return to you. Nothing is retained on our side beyond inventory metadata.
SOC 2 path in progress
Type I target: Q4 2026. Type II follows. We will not claim certification we do not hold.

Pricing

One tier while we build. Enterprise when you need it.

Starter

$0 / platform / during early access
  • Up to 3 connected platforms
  • Monthly inventory, delivered as report
  • Metadata-only retention by default
  • Email support, direct line to the team
Run inventory

Enterprise

Talk to us
  • All connected platforms, all workspaces
  • Continuous inventory with change alerts
  • SSO, custom retention, regional residency
  • Shared channel with our team
Contact the team

Run inventory

Begin the excavation.

Early access is free while we build v0.1. You receive the first inventory and a direct line to the team.

One email when v0.1 is ready. That is it.