
iPaaS Pricing Explained for HR, Payroll and Benefits Teams (2026)

Summarise the blog with AI
Last verified: 2026-11-20
iPaaS pricing is one of the least transparent categories in enterprise software. Vendors use different models (per connector, per transaction, per user, per workflow) and the actual cost often doesn't become clear until you're deep into implementation or hitting usage limits you didn't anticipate.
HR, payroll and benefits integrations make that worse. Volume is uneven: a new employer's first backfill, a hiring wave and open enrollment can multiply a month's traffic. Payloads carry employee records and census files. And the systems you connect to belong to your customers, not to you.
This guide breaks down how iPaaS pricing works, what the major vendors actually bill for in 2026, where hidden costs appear after go-live, and how to evaluate total cost of ownership before committing.
Key takeaways
- The pricing model decides cost more than the sticker price. Per connector, per transaction, per user, flat subscription and per customer connection each reward a different workload, so start by counting your own workflow in each vendor's unit.
- One workflow, very different counts. The same 2,000-run HR onboarding workflow is 2,000 n8n executions, 6,000 Zapier tasks or Make credits, and 14,000 Boomi messages.
- Check expiry, base fees and eligibility before you compare rates. Workato Pro credits expire at month end, Boomi's $99 base fee applies at zero usage, and Boomi Pay-As-You-Go is currently open only to active trial users.
- Hidden costs sit outside the rate card. Premium connectors, support tiers, implementation services, overage rules and in-house maintenance often decide the real bill.
- Plan for HR's peaks. Per-transaction pricing is cheapest in a quiet month and most expensive during open enrollment.
- Customer-facing integrations are a different purchase. A product that connects each customer's HRIS or payroll system is usually priced per connected customer, which tracks your revenue rather than your call volume.
Common iPaaS Pricing Models
There are five models in common use. Most vendors blend two of them, for example a platform edition plus a usage meter.
Per Connector
You pay for each system integration you activate. Simple to understand, but it becomes expensive quickly if you need broad HRIS coverage, because every HRIS, payroll system and benefits carrier counts as a separate connector. Jitterbit's pricing page packages Harmony editions by connection count: 2 to 3 on Standard, 5 on Professional and 8 or more on Enterprise. Celigo prices by endpoints and flows, through custom quotes, and says on its pricing page that there are no overage fees.
Per Transaction / API Call
You pay based on data volume or call frequency. Predictable at low volumes, potentially expensive at scale. This is the most common model in workflow automation, and every vendor names its unit differently: Zapier counts tasks, Make and Workato credits, Boomi messages, n8n executions, Oracle Integration message packs and Azure Logic Apps actions and calls. The next section shows how far apart those units are.
Per User / Per Seat
Pricing tied to the number of people, or bots, licensed. Common for collaboration and productivity tools, less common for pure integration infrastructure. Microsoft Power Automate is the main example: Premium is $15 per user per month and Process is $150 per bot per month, both paid yearly, US list prices.
Flat Subscription
A fixed monthly or annual fee for a defined set of connectors or workflow capacity. Easier to budget, but limits flexibility if you need more connectors or higher volume. SAP Integration Suite sells editions at USD 1,727, 5,336 and 7,685 a month, with the starter edition including 50,000 messages and 10 custom integration flows. MuleSoft packages start at $2,000 a month, billed annually, and draw on a shared pool of Mule Credits.
Per Connection (Customer-Facing)
For platforms embedding integration into their product, pricing is often per active employer or customer connection. This aligns cost with revenue growth: you pay more as more of your customers connect their systems, not as each one sends more data. Paragon bills by Connected Users, which its docs say typically represent one of your customer organizations. Bindbee prices per active customer connection, with unlimited API calls, syncs and webhook events.
How the billing units compare on one HR workflow
A dollar figure means something only once you know what is being counted. Even the open billing-data standard offers no shortcut. The FinOps Foundation's FOCUS specification extended its schema to SaaS and PaaS cost and usage in version 1.2, and it records the consumed unit as a provider-specified measure. There is no common unit to convert into, so the conversion is yours to do.
Take one workflow and carry it through. An HR onboarding automation runs 2,000 times a month. Each run receives a new-hire record, then makes three calls out: create a directory account, post to chat, update a sheet.
On Zapier those three actions are 3 tasks a run, so 6,000 tasks a month. On Make, three module actions are 3 credits a run, 6,000 credits. n8n's cloud plans count one execution for each full run of a workflow, however many steps it has, so the same month is 2,000 executions. Boomi counts a message for every inbound and outbound document, including the response document from a request/response call: one document in, three out and three responses back is seven messages a run, so 14,000 messages a month.
None of those numbers says which is cheaper until you know what each unit costs. The table sets out what increments each unit and what to count in your own workflow:
Bindbee's guide to what an API integration costs covers the build-side half of the same budget.
What the major iPaaS vendors charge in 2026
Every figure below is the vendor's own, from its pricing or docs pages, with the billing cadence the vendor states.
Zapier
Professional is $19.99 a month for the 750-task starting tier and Team is $69, both billed annually; monthly billing costs more ($29.99 for Professional). Filters and Paths don't consume tasks, and a step that fails isn't charged. Since 15 June 2026, AI by Zapier steps cost 1, 3 or 5 tasks by model tier, and Premium, at 5, is the default for new AI steps. Swap one of the onboarding workflow's actions for a default AI step and each run costs 7 tasks, which is 14,000 a month. Overage is billed at 1.25× the cost of a base task, capped at 3× the task limit.
Make
One credit per module action. At the 10,000-credit tier, billed annually, Core is $12 a month, Pro $21 and Teams $38, with Free at 1,000 credits and Enterprise custom. Data transfer is capped at 5 GB per 10,000 credits, which matters for workflows that move census or payroll files. Free also has a 15-minute minimum interval between runs.
Workato
Pro runs from $75 a month for 2,500 credits up to $1,275 for 50,000, billed monthly, and Enterprise is custom-priced with unlimited users. Workato's landing page leads with the 3,500-credit tier at $100, so both figures appear in quotes. Only successful completed operations count, reruns count, unused Pro credits expire at month end with no rollover, and Pro supports up to 3 users per workspace. On the 2,500-credit tier, a quiet month that uses 1,800 credits forfeits the other 700.
Boomi
Pay-As-You-Go is $99 a month plus $0.05 per message, with unlimited users, connections and environments and no annual contract. The $99 base fee applies even in a month with zero messages, and the plan is currently available only to active trial users, so price it during Boomi's 30-day trial. It includes Standard support, which can't be upgraded.
Power Automate
Microsoft says the prices on its pricing page are for marketing purposes and may vary by currency, country, region and organization, so these are US list prices: Premium $15 per user per month, Process $150 per bot and Hosted Process $215 per bot, all paid yearly. On price alone, one Process bot costs the same as ten Premium users, but the licences cover different flows: Premium covers cloud flows and attended desktop flows, and Process covers unattended desktop flows.
n8n
The self-hosted Community Edition carries no licence fee; the hosting is yours to supply and run. The cloud plans are metered in executions: Starter $20 a month for 2,500, Pro $50 for 10,000 and Business $800 for 40,000, all billed annually. The execution meter rewards long workflows and penalizes frequent ones: a trigger that fires every minute is 43,200 executions a month, whatever it does when it fires.
MuleSoft and SAP
MuleSoft packages start at $2,000 a month, billed annually, with a $50K minimum annual commitment on the Pre-Commit option. SAP Integration Suite's editions run from USD 1,727 to 7,685 a month. Both suit enterprises integrating their own estate, and both are covered in more depth in our guide to the top enterprise integration platforms.
Hidden Costs to Watch For
The rate card is the visible part of the bill. These are the costs that tend to appear after go-live.
Open enrollment and other HR peaks
Per-transaction pricing is cheapest in a quiet month and most expensive in your busiest one. In benefits, that is open enrollment, when elections, dependents and deductions change for most employees at once. Onboarding a large employer creates the same spike, because its first sync pulls every employee record. Price your peak month, not your average one, and check whether unused capacity rolls over.
File-heavy payroll and benefits data
HR integrations often move files: census exports, payroll registers, carrier enrollment files. Some meters count file size as well as runs. Oracle Integration counts payloads over 50KB as extra billing messages, and Make caps data transfer at 5 GB per 10,000 credits. If your workflow moves files, count bytes as well as runs.
What leaving costs
Leaving is the other half of a commitment. From 12 January 2027, the EU Data Act (Regulation (EU) 2023/2854, Article 29) bars providers of data processing services from charging customers switching charges for the switching process. Until then, charges are limited to cost. It applies to EU customers of data processing services.
Matching a pricing model to your HR workload
Pick the model your workload stresses least, then trial two tools on the same workflow.
Count the workflow in each tool's unit before the trial starts, then let the trial confirm the count. Zapier's Professional trial runs 14 days and Power Automate's runs 30, so a prior estimate is what makes a short trial useful.
When the integration is a product feature
The tools above are bought to automate work you run. A benefits platform, payroll app or HR Tech product has a different problem: it needs to connect each of its customers' own HRIS and payroll systems. That is a customer-facing integration, and a different purchase.
A unified API gives your product one API and one normalized data model across your customers' systems, with each customer authorizing their own. The question it raises is how many of your customers' systems you can connect, and what that costs as the number grows. Bindbee's explainer on unified APIs versus workflow and ETL tools covers the category difference in depth, and Bindbee's comparison with Workato covers where a recipe platform stops and a product integration starts.
How Bindbee Approaches Pricing
Bindbee uses a per-connection model aligned to your customer base: it prices per active customer connection, with unlimited API calls, syncs and webhook events. As you add employer clients, costs scale predictably with them, and an open enrollment month costs the same as a quiet one.
That connection gives you one API across 110+ HRIS, payroll, ATS and benefits systems, with 40+ unified data models, and Bindbee maintains the connectors, so there's no hidden engineering overhead when a vendor changes its API. Bindbee reads and writes through the same API, though write support varies by model and integration; per-integration model support is published in Bindbee's Model Availability Matrix, so check coverage before you plan around it.
Your customers authorize their own systems through a hosted Magic Link or an Embedded SDK, and their credentials never pass through your product. Bindbee is SOC 2 Type II compliant, which matters when the data is employee records. We build the integrations. You build the product.
FAQ
How is iPaaS priced?
Most iPaaS vendors use one or a blend of five models: per connector, per transaction or API call, per user or seat, flat subscription, and per customer connection for products that embed integrations. Each vendor names its unit differently (tasks, credits, messages, executions, actions), so compare by counting your own workflow in each unit.
What hidden costs should I expect from an iPaaS?
Premium or enterprise connector fees, support and SLA tiers, implementation services, overage or true-up charges, add-ons such as on-premise agents, and the engineering time to maintain integrations. For HR and benefits data, also price your open enrollment month and any file-heavy workflows.
Is Zapier fully free?
Not fully: Zapier has a free plan of 100 tasks a month, but it is limited to two-step Zaps. Multi-step Zaps, premium apps and webhooks need a paid plan, according to Zapier's pricing page.
What counts as a task in Zapier, a credit in Make and an execution in n8n?
A Zapier task is one successful action step, and AI by Zapier steps cost 1, 3 or 5 tasks by model tier. A Make credit is one module action. An n8n execution is one full run of a workflow, whatever the step count. A three-action workflow that runs 2,000 times a month is 6,000 Zapier tasks, 6,000 Make credits and 2,000 n8n executions.

Book a demo to discuss how Bindbee's pricing fits your integration needs.





