Tracking 5 Automation Vendors: USTA Pricing Index

The USTA Automation Pricing Index tracks what automation vendors publish on their own pricing and changelog pages — and seals that state with a content hash so any future change is detectable. This is the baseline edition, captured on June 26, 2026, with no prior snapshot to compare against. Every figure in this report was present in static HTML on that single sealed day.

This baseline covers 5 vendors across 7 sources: ActiveCampaign, GoHighLevel, Keap, n8n, and Zapier. Because every source hash is new, every entry is logged as "baseline" and no trend claims can be made. That changes with the next snapshot, when the clock has a prior hash to diff against.

What the Baseline Captures

The index records the exact price figures a pricing page displays on the fetch date — not what those figures mean, and not how they map to named plan tiers. Three of the 7 sources in this baseline carried detectable price figures in static HTML. The remaining sources are either changelogs (no prices expected) or client-side rendered (zero static figures, not $0).

Zapier's pricing page showed 28 distinct price figures.

GoHighLevel's pricing page showed 15 distinct price figures.

Keap's pricing page showed 12 distinct price figures.

n8n renders pricing client-side through embedded JavaScript. The static HTML returned by a standard fetch contains 14 price keys in embedded JSON but zero rendered price points in the HTML itself. USTA reports n8n at zero static figures, not $0, because "$0" would imply a free tier rather than a rendering limitation. ActiveCampaign's tracked source in this edition is a changelog, not a pricing page, and carries no price figures — that is expected and not a gap.

The at-a-glance summary for this edition:

How the Clock Captures Prices

The automation-pricing clock fetches each source URL, computes a cryptographic content hash, and records it. On the next fetch it diffs the new hash against the stored one. A matching hash means the page content is identical to the prior snapshot. A different hash means something on the page changed — which triggers an investigation into what changed and whether it was a price figure.

On the first seal there is no prior hash for any source, so every source registers as "baseline." No change is claimable because there is nothing to compare. Sources changed is 0 for this edition. Starting with the second edition, hash deltas will be reported as changes and the affected source's new figure list will be shown alongside the prior list.

Price figures are extracted from static HTML using a strict canonical currency form. They must be well-formed dollar values, deduplicated within the source, and clamped to the band [$1, $100,000]. Figures below $1 are excluded. Figures above $100,000 are excluded. The clock does not compute averages, minimums, or plan mappings from the raw figures.

"Client-side-rendered sources expose zero static figures and are reported as such, not as $0 — because $0 implies a price, not a rendering architecture."

Sources that render prices through JavaScript after page load, like n8n, appear blank to a standard content fetch. The 14 price keys found in n8n's embedded JSON are noted in the source record but not extracted as display prices, because they are not rendered to static HTML. This is a data-quality transparency note, not a judgment on n8n's pricing model.

For context on how USTA tracks AI-tool pricing across the automation ecosystem, see USTA's AI Price Index for June 2026.

The Seven Sealed Sources

Each source is sealed with a cryptographic content hash (truncated to 12 hex characters for display). The role field describes why the source is included: "changelog" sources track product update cadence; "price" and "price_anchor" sources track pricing page state; "price_reference" sources provide supplemental plan documentation.

The full content hashes for this seal are: ActiveCampaign 4db35ed0ff6e; GoHighLevel 410fc39a7c81; Keap ce28e3b1f82b; n8n release notes b51c21d2dda8; n8n pricing ca6065f1180a; Zapier pricing 9a98e92179c5; Zapier plans help 630c2a24aa96. These hashes are the audit trail. If the same source URL is fetched again and the hash differs, the clock flags a change for review.

Zapier is tracked across two sources — a primary pricing page (price_anchor) and a plans help document (price_reference) — because Zapier's published plan documentation is split across more than one page. The pricing anchor page is the primary source for figure extraction.

Observed Price Figures by Vendor

The table below lists every distinct price figure observed in static HTML on June 26, 2026. These figures are copied verbatim from the page — not normalized, not attributed to named plan tiers, and not ranked by size. The order reflects extraction order, not price order. No minimum or starting price is asserted for any vendor.

Zapier displayed 28 figures on a single pricing page — the widest observed figure set in this baseline. The range spans $1 to $800. That breadth reflects the complexity of Zapier's plan structure, which includes per-task pricing, seat-based pricing, annual and monthly equivalents, and add-on pricing. None of those figures can be attributed to a specific tier from the static HTML alone.

GoHighLevel's figure range extends from $10 to $4,970. The presence of figures like $2,970 and $4,970 alongside $10 suggests the page surfaces agency, white-label, or enterprise tiers alongside entry-level prices. No tier attribution is made here.

If you are evaluating workflow tools and need practical tradeoff context beyond raw prices, the Zapier alternatives guide for Shopify ecommerce examines real operational factors beyond list price.

Why the Lowest Figure Is Not the Entry Price

A common pattern on SaaS pricing pages is to display many figures simultaneously: monthly and annual rates for the same tier, per-seat prices, per-task add-ons, legacy plan prices, and promotional anchors. The lowest dollar figure on the page is rarely the actual cost to get started with the product.

Zapier's pricing page shows $1 among its 28 figures. That does not mean $1 is the cost to use Zapier. It may represent a per-task rate, a promotional price, or a fragment of a per-unit calculation. GoHighLevel shows $10 among its 15 figures. Again, no entry-price claim is made. Reading the surrounding page context is required to interpret any individual figure.

"The price figures shown in this index are what the page displayed on one sealed day — they are a census of published numbers, not an offer, not a recommendation, and not a minimum cost to onboard."

This is not a limitation of the index — it is the point of the index. By capturing every figure the page shows, USTA creates an objective record. When the figure list changes in a future edition, you know the page changed. Whether that change represents a price increase, a plan restructure, or a promotional addition is context you bring from reading the live page at that moment.

For teams working through pricing decisions in financial workflows, the accounting firm workflow automation pricing guide provides context on how SaaS plan tiers translate to per-workflow cost in practice.

Frequently Asked Questions

Q: Why does n8n show zero price figures when it clearly has a paid plan?
A: n8n's pricing page renders price figures through JavaScript after the initial HTML is delivered. A standard content fetch receives the HTML shell and embedded JSON — which contains 14 price keys — but no rendered dollar values in the static markup. USTA reports this as a client-side rendering limitation and logs zero static figures, not $0. The distinction matters because $0 implies a free tier rather than a data-availability constraint.

Q: What does "baseline" mean in the Change column?
A: This is the first seal for all 7 sources. Because there is no prior content hash on record, every source registers as "baseline" and sources changed is 0. Starting with the second edition, any content hash delta will be flagged as a change and the affected source's updated figure list will be shown alongside the prior list for comparison. Trend claims require at least two snapshots.

Q: Are the price figures monthly or annual rates?
A: The index does not classify figures by billing period. The figures listed are exactly what appeared in static HTML on June 26, 2026 — monthly rates, annual equivalents, per-seat prices, and other figures may all appear on the same page simultaneously. No billing-period attribution is made in this report.

Q: How often is the index updated?
A: The automation-pricing clock fetches and hashes sources daily. A new sealed edition is published when a content change is detected in one or more sources, or on a scheduled cadence. This baseline edition establishes the starting state. Future editions will report hash deltas and updated figure lists for any source that changed.

Q: Can I use these figures to compare which vendor is least expensive?
A: Not directly. The figures are vendor-specific page observations captured on the same day — they are not normalized to equivalent plan tiers, seat counts, or feature sets. Comparing $10 from GoHighLevel to $9 from Keap does not tell you which is cheaper for your use case. The index is designed to track when pricing pages change, not to rank vendors by cost.

Put the Pricing Index to Work

A RevOps lead evaluating automation vendors spends real time checking pricing pages manually — and those pages change without notice. Vendor pricing updates rarely generate press releases. By the time a contract renewal arrives, a tier that existed at the last eval may have been restructured. The USTA Automation Pricing Index removes the need to catch these changes manually by sealing the page state and detecting hash deltas automatically.

US Tech Automations turns that sealed data into actionable workflow signals. When a vendor's pricing hash changes, a USTA-built workflow can route an alert to your Slack channel, log the event to a CRM field, queue a re-evaluation task for your operations manager, and timestamp the change — all without a human checking the page. That is what it means to automate vendor price monitoring at the operations layer.

Operations managers and procurement teams who run regular vendor reviews benefit most from this index. Baseline today; measure the delta at renewal. If a vendor's figure list changes between now and your next contract decision, you have a timestamped record of what changed and when. The accounting automation ROI framework demonstrates how to anchor that kind of operational data into a total-cost model for finance teams.

Data, Scope, and Methodology

Source: US Tech Automations automation-pricing clock (peer-platform pricing & changelog pages, fetched and content-hashed daily).

Scope: Point-in-time published pricing and changelog state for the automation/orchestration platforms USTA is genuinely compared against (ActiveCampaign, GoHighLevel, Keap, n8n, Zapier), captured by the USTA automation-pricing clock on June 26, 2026.

Honesty: Price figures are the distinct, well-formed dollar values shown on the page the clock actually fetched — validated to a canonical currency form, deduplicated, and clamped to the band [$1, $100,000]; nothing is estimated, modeled or extrapolated. They are NOT mapped to named plan tiers and NO minimum or starting price is asserted: the lowest figure on a marketing page is usually not the entry plan price.

A change is a content hash delta versus the most recent prior snapshot; the first seal is a baseline with no prior to diff. Sources that render prices client-side (n8n) expose zero static figures and are reported as such, not as $0.

Baseline edition note: Because this is the first seal for all 7 sources, there are no prior hashes to compare. No trend claims, price-increase assertions, or conclusions about which vendor raised or lowered prices can be drawn from a single snapshot. Those analyses become possible starting with the second edition.

Source: US Tech Automations Research — computed from the sealed automation-pricing snapshot, June 26, 2026.