Zapier's app directory is a live market map

Zapier's app directory has somewhere north of 7,000 integrations in it. Most people treat that number as a marketing stat — proof the platform connects to everything. It's more useful read the other way. Every one of those listings is a decision someone at Zapier made about where a build hour was worth spending. Line them up, sort them, and the directory stops being a catalog and starts being a ledger of intent.

You don't need access to anyone's roadmap to read it. The whole thing sits at a public URL, updates on its own schedule, and asks nothing of you but attention.

The directory is a partnership ledger

A new app in the directory is rarely a solo effort. Integrations get built because a partnership got signed, a category got prioritized, or a big customer asked loudly enough. So the flow of new listings is a running record of who Zapier is choosing to get close to.

Filter the directory to recently added apps and the pattern usually clusters. Three new fintech tools in a month is not three coincidences — it's a category Zapier decided was worth courting. A sudden run of AI-writing or vector-database integrations tells you where they think the next wave of demand is, weeks before anyone frames it as strategy in a blog post.

The absences say as much as the additions. A well-funded competitor category that isn't in the directory is a deliberate gap, a bet-against, or a relationship that soured. Note what's missing, not only what showed up.

"Popular" and "New" are ranked priorities

Zapier sorts. The directory surfaces popular apps, featured apps, and new apps in ways that aren't neutral — placement is an editorial choice, and editorial choices leak priorities.

Watch which apps get pulled into the "featured" or "popular" rails over time. When a category you compete in starts getting front-page real estate, that's Zapier telling its whole user base where to look. If your own space quietly drops off the featured rail, that's a demotion you'd never get told about directly. The ranking is a public statement of what Zapier wants its users to adopt next, and it moves.

This is the kind of shift that looks like nothing on any single visit and obvious across three months of them. It's the same logic behind spotting a competitor pivot before they announce it — the signal lives in the drift, not the snapshot.

Trigger and action counts show real investment

Open any single app's page and you get its list of available triggers and actions. That count is the honest measure of how much Zapier actually invested in a connection, stripped of the marketing gloss.

A "we integrate with X" listing that offers one trigger and no actions is a check-the-box integration — built to claim coverage, not to be used. Fifteen triggers and twenty actions is a connection someone maintains, tests, and cares about. When you see a competitor's integration on Zapier grow from three actions to twenty over two quarters, that's a relationship deepening in plain view. The depth number is harder to spin than the mere presence of a logo, which is exactly why it's worth tracking.

This is the granular end of what an integration page can signal: not just that two products connect, but how seriously.

Templates reveal the demand they see

Zapier publishes pre-built Zap templates — "when this happens in App A, do that in App B." Each template is a small hypothesis about a workflow enough people want that it's worth packaging.

Read the templates tied to your category and you're reading Zapier's model of what your shared users are actually trying to do. Which apps get paired with which. Which use cases get named. A cluster of new templates connecting a competitor to a specific vertical tool tells you that competitor is being pulled toward that vertical — by real demand, not by a press release. It's one of those overlooked surfaces that sits in the open precisely because it looks too mundane to be strategic.

What this teardown misses if you check it once

Everything above depends on comparison across time. A directory read once is trivia; the same directory read against its own past is a signal. The new apps only mean something relative to last month's list. The featured rail only moves if you remember where it sat. The trigger counts only tell a story as a trend line.

That memory problem is the whole reason a surface like this goes unwatched — nobody wants to screenshot a 7,000-app directory every week and diff it by eye. This is the narrow thing Seeto does: it monitors public surfaces like a competitor's directory listing or integration page continuously and surfaces the changes as discrete events — this app appeared, that action count grew, this listing got featured. It doesn't interpret Zapier's strategy for you or summarize the market. It just makes sure the drift doesn't slip past you, so the reading — the part that needs your judgment — is the part you actually get to do.

Pick one competitor. Find their Zapier page and the templates around them. Look at it today, then look again in a month. The gap between the two readings is the intelligence — and it was public the entire time.