Some nodes call an API. Others do the whole job.
All the endpoint nodes you would expect are here, for the services you already run. Sitting alongside them are worker nodes, where transcribing a recording or building a keyword universe is one node instead of a pipeline you maintain.
Moving data is the easy half.
Endpoint nodes are the right tool for moving a record from one place to another, and every builder including this one is full of them. Zapier, Make, and n8n are genuinely good at that job.
The harder half is the operation itself. "Transcribe this and pull out the decisions" is not an endpoint. It is several of them, plus prompt design, plus retries, plus the format you wanted at the end. Everywhere else, that part stays yours to build and yours to maintain.
-
You are the systems integrator
Real operations mean chaining several services and owning every seam between them
-
Every step you add is a step you pay for
Most usage-based tools charge per action, so the thorough version costs more every time it runs
-
A separate bill for a separate platform
Automation arrives as its own subscription, on top of the tools it is automating
-
Or you run the infrastructure yourself
The self-hosted route trades the bill for setup hours and ongoing maintenance
Free to open. Your plan already includes runs.
Automations is an Engine, so it is not sold per seat, and every paid plan on the Mattering platform includes credits. Anyone in your organization can open it, and every run draws from one shared org pool.
That pool is filled by the plan you already have. Most teams never buy an automation plan at all, which is the honest answer to why this is not just another automation bill.
Runs per month, pooled across the whole organization. The All-App Pass is $25 per seat per month and reaches every premier app, which is why it carries the richer allowance.
Per run, not per action.
Most usage-based automation tools charge per action, so every step you add costs more each time the workflow runs. We charge per run, regardless of how many actions are in it.
A workflow with 30 steps costs the same to run as one with three. Build the version with the error branch and the extra lookup, because the design stops being a billing decision.
Some jobs should not be a pipeline.
Most of what you build will use ordinary nodes, and that is fine. But for a handful of jobs that would otherwise be a pipeline you design, prompt, and babysit, we ship a worker node instead.
Each one already handles the retries, the rate limits, and the shape of the output. You still wire the logic. You just do not have to invent the operation.
Operations that ship
as one node.
-
Search research: keyword universes, SERP collection, topic clustering
-
Media: transcription with word timings, frame extraction
-
Video: timeline assembly and rendering
-
Web and files: page extraction, document operations
-
Market research, returned as structured output
It talks to the tools you already run.
Connect a service once and its nodes appear in the palette. The credential lives with the connection, so handing a workflow to someone else does not break it.
Mattering nodes arrive connected
Productivity triggers, queries, and actions are native. No API key to mint, no webhook to register, no OAuth dance, because they are part of the same platform rather than a product you are integrating with.
Databases for the state in between
Workflows need somewhere to keep things. Databases live in Automations, so a run can write a row, read it back next week, and drive the next decision from it.
Nothing to self-host
No container to run, no upgrades to schedule, no server to keep alive at 2am. Credentials sit in a secrets layer with per-person grants and an access log.
Add runs when you actually need them.
These are org-level plans, and they stack. A plan counts as a paid subscription, so the 20,000 base comes with it, and your seats add on top of that.
Starter
For simple workflows
$15 per month
22,500 runs per month
2,500 from the plan, plus the 20,000 base
- Basic triggers and actions
- 7-day execution history
Pro
For growing teams
$49 per month
30,000 runs per month
10,000 from the plan, plus the 20,000 base
- Advanced logic and branching
- Webhooks and external APIs
- 30-day execution history
Scale
For power users
$149 per month
70,000 runs per month
50,000 from the plan, plus the 20,000 base
- Everything in Pro
- Real-time triggers
- Unlimited execution history
Busy month rather than a bigger baseline? Top-up packs are $7 per 1,000 runs. See the full pricing page
Build the thorough version.
Open Automations, drop in a worker node, and watch a four-node run cost one credit.