What looks wrong?

We say this article was researched and checked. If it is wrong, we want the counter-example.

Skip to content
Wendell Achterberg

Nov 22, 202616 min read

Restricting app connections: the short answer and comparison

The short answer: top picks and who each is for

Until a platform shows an admin-set allow-list that blocks a connection before it exists, it earns no pick here.

If you are already inside a Microsoft estate, you will look first at Power Automate, which documents admin policies over connectors.

If you must keep data on your own servers, you will look at n8n and Activepieces, where the question is whether the control survives self-hosting.

Activepieces has an MIT-licensed core and keeps its enterprise directories under a separate commercial licence, so the line between free and paid can be read in the repository.

How the platforms were assessed

When someone tries to create a connection, the platform checks it against a rule an administrator wrote about which apps a workflow may connect to. That is what restricting an app connection means here.

A report listing connections after the fact is an audit, and the connection has already moved data by then.

You can run each platform through three tests, in this order:

  1. Where the control lives: at connection creation, or only in a later review.
  2. Which plan unlocks it, because a control sold only at the top tier is not available to a team on a lower one.
  3. Whether it still applies when you run the software yourself, since a cloud-only control disappears the day you self-host.

Read the table as what each vendor documents and where its page is silent; it reflects vendor pages as of 2026-11-22. A "Not confirmed" is a question to put to the vendor in writing.

Platform List price Strength Limit Best for
Zapier Not confirmed Wide catalogue of app connections Allow-list plan and self-hosting: not confirmed Teams that will verify admin controls by contract
Make Not confirmed Not confirmed Not confirmed Buyers prepared to request documentation
n8n Not confirmed Can be self-hosted Whether an allow-list applies when self-hosted: not confirmed Teams that must run on their own infrastructure
Workato Not confirmed Enterprise governance positioning Connection-level enforcement: not confirmed Buyers with a formal approval chain
Power Automate Not confirmed Admin policies over connectors Plan required: not confirmed Organisations already managing Microsoft environments
Activepieces Free; Team $200 a month; Ultimate through sales MIT-licensed core, 750 integrations, can be self-hosted Allow-list enforcement: not confirmed Teams that want to test self-hosted control first

Settle any "Not confirmed" in that table in the contract before signing.

Everything below works on Activepieces' free plan. Start without code or a credit card.

1. Activepieces for self-hosted teams

If the question is which integrations a team may use, Activepieces documents admin control over it. The self-hosted position below the paid tier is the part to put to the vendor in writing.

Per Microsoft, Hosted Process is $215 per bot per month, which adds $65 per bot for Microsoft to host the machine the bot runs on, so only about 30% of the monthly fee is direct infrastructure cost.

A small server box sitting on a tiny stool, beside a heap of coins more than three times its size.

Documented app connection controls versus open questions

To separate what the documentation and pricing page support from what they leave open, use the list below. Treat the first group as the claims you can cite in a purchase request, and the rest as questions.

  • The Plus plan on the cloud product is $20 a month flat, published on the pricing page, so the entry cost is checkable before you sign.
  • Plus includes 10,000 credits a month and up to 5 users, which means a team should size its flows (Activepieces' term for an automation) against them before buying.
  • The docs describe platform administrators managing integrations, so the control sits with the admin, not with each flow builder.
  • Nothing on the pricing page says that control is free on any plan.

You will not learn from any of that whether the control blocks a connection before it is made. Those points only tell you where to look, so ask for the setting by name.

Self-hosting and open questions

You can run Activepieces on your own infrastructure, with an MIT-licensed core, and that's the reason it's on this list. The open question is whether admin control over integrations comes with the self-hosted install or sits behind a paid licence.

Ask for that answer in the contract, not in a support chat.

The documentation leaves three things open. The first is whether the free self-hosted edition includes integration control. The second is whether a flow can reach a restricted integration by another route. The third is whether the platform enforces the allow-list before anyone creates a connection.

Activepieces pricing page showing four subscription tiers with features and pricing.

Until the vendor confirms each in writing, treat them as unmet.

If your team wants to run the platform on its own servers and is willing to pay for the licence that unlocks admin control, this is the best fit.

It's a poor fit for a buyer who needs the enforcement guarantee on a free self-hosted install today.

Activepieces may suit security-conscious teams that need to run automation in an air-gapped environment, though which enterprise features come with the self-hosted install is unconfirmed.

The claim the article rests on is that the list, which covers SSO, SCIM, custom RBAC, audit logs, release management and secret managers, is the same in the self-hosted air-gapped docs as on the managed cloud pinned to an EU or US region with SOC 2 Type II, so choosing full control does not mean accepting a fraction of the product.

The section's own caveat still applies: the docs confirm admin-level control over integrations, but a team should get in writing what the self-hosted position includes below the paid tier before it buys.

2. Power Automate for tenant-wide policy

A disallowed connector never reaches a flow. Power Automate enforces connector restrictions through data loss prevention (DLP) policies, which an administrator sets for the whole tenant and which block it before any flow can use it.

How connector restrictions work

Once an administrator sorts each connector into one of three groups, Business, Non-business or Blocked, the rules follow. A flow can't combine connectors from the Business and Non-business groups, and it can't use a Blocked connector at all.

Three trays side by side holding connector cards: Business, Non-business and Blocked.

Power Automate stops a violating flow when someone saves or runs it, not in a later review.

You can set a policy for every environment in the tenant or only for chosen ones. A tenant-wide policy is the closest match to a central allow-list, because individual makers can't opt out of it.

Power Automate Premium plan and connector pricing

$15 per user per month is the Premium plan's price on Microsoft's pricing page. Premium connectors are generally the ones a policy needs to govern, so each maker who builds with them needs a seat, and cost grows with headcount.

Activepieces pricing page with four subscription tiers showing features and monthly costs

$150 per bot per month is Microsoft's Process price, so a single bot costs the same as ten Premium users. Microsoft prices unattended robotic process automation per bot.

Per Microsoft, Hosted Process is $215 per bot per month, which is $65 per bot more than Process and includes a Microsoft-hosted machine for the bot.

The organization's monthly costs therefore scale linearly with the number of bots deployed.

Settle with Microsoft in writing which licence tier covers the admin tooling, since the pricing page doesn't say.

Limit and best for

Every connector needs a classification decision, and a catalogue that Microsoft keeps extending leaves the policy owner with new connectors to review. That is the limit: administrative weight.

When policies are layered across tenant and environment, they can also conflict, so someone must own the ruleset and test it. Licensing adds a second layer of approval beside the technical one.

If your organisation is already on Microsoft 365 and has a platform administrator and a change-approval process able to maintain a classification list, this model suits it. It's a poorer fit for a small team with no one to own that list.

Easier to see it running than to read about it: set it up free, no card.

3. Workato for enterprise governance

Where an approval chain already exists for who may connect which application, Workato is the one to suit. It publishes no price, so confirm with the vendor which tier carries the controls.

For restricting connections, Workato's documentation describes three layers:

  • Controls over which connectors may be used
  • Separation of work into distinct workspaces
  • Role-based permissions over who can build, deploy and administer

Together they allow an administrator to decide in advance what a builder may connect to, rather than reviewing connections after they exist.

Read the documentation for what each control does, then treat what it doesn't state, namely which plan includes each one, as an open question.

Workato pricing and connector control availability

You will not find a Workato price on any public page, because it sells by quote. It publishes no list price or tier-by-tier feature comparison, so a buyer can't check from public pages which plan includes connector controls or role permissions.

Activepieces pricing page showing four subscription tiers with features and monthly costs.

For a procurement file this is the central gap: a control that exists in the documentation but sits in a tier you didn't buy isn't a control you have. The questions below close that gap, because you can write the answers into the order form.

  • Which tier includes connector controls, and does the platform enforce that control before it creates a connection?
  • Which tier includes workspace separation, and can it keep one team's connections from another's?
  • Which tier includes custom role permissions, and what can an administrator restrict?
  • How's enforcement evidenced: an audit log, an export, or a report you can hand to an auditor?
  • What's the contract term, and can you move tiers within it?

Ask for the answers in writing and attach them to the contract. A verbal assurance from sales won't satisfy an auditor.

Until you have a quote in hand, you can't compare Workato with platforms that publish their plans. That is the limit: opacity. It's best for large organisations with a named owner for the allow-list and a procurement process able to negotiate tier and term.

Activepieces gives the self-hosting half of that question a list you can lay side by side.

The air-gapped self-hosted docs and the managed cloud docs describe one and the same set of enterprise controls: single sign-on, SCIM provisioning, custom roles, audit logs, release management and a hook into your own secret manager.

The cloud can sit in Frankfurt for EU data, and nothing drops out when the servers are yours. MoneyGram, Moneypenny, Alan and FundingSocieties run Activepieces in production.

4. Zapier for team admin controls

On Zapier the app allowlist sits on the Enterprise plan, which suits an organisation that has a named owner for the list and a procurement process able to negotiate tier and term. Zapier is the workflow automation service whose controls are assessed here.

App restrictions for team and enterprise accounts

Before the benefit, the audit point: an allowlist is only worth buying if the administrator can show which apps are permitted and who changed that list.

When a member tries a disallowed connection, it is refused rather than found in a later review. Zapier's help pages describe the allowlist as an Enterprise control that lets an admin limit which apps members can connect. That's the property this comparison is looking for.

Whether the change history is exported is not confirmed by the pages reviewed, so ask for it in writing.

Beside Zapier, the table sets Make, a visual automation service, and n8n, a workflow tool offered both as a hosted cloud and as software you run yourself.

It shows that Power Automate's and Zapier's controls are confirmed by the pages reviewed, so the other rows are open questions to put to the vendor, not findings against them.

Platform Plan needed List price What the admin can restrict Items not confirmed
Zapier Enterprise Not confirmed here Which apps members can use, through an app allowlist Audit trail of list changes
Make Not confirmed Not confirmed here Not confirmed Any admin allowlist of apps
n8n cloud Not confirmed Not confirmed here Not confirmed Any admin allowlist of apps
n8n self-hosted Not confirmed Not confirmed here Not confirmed Whether the control exists, and on which licence
Activepieces — — — Any admin allowlist of apps

What each Power Automate licence tier costs

Because no list price is confirmed for any row, request a written quotation stating the tier and the term before comparing cost.

The limit is evidence. Zapier's allowlist is confirmed, but its price and audit detail are not, and nothing confirms equivalent controls for Make or either n8n deployment.

For n8n self-hosted, whoever runs the server controls what is installed, which is a different thing from an admin-enforced allowlist. Ask each vendor for the plan page, the admin setting by name and the contract clause that commits to it.

A person with a ring of keys at a server rack, freely adding things to the shelves, while a velvet-rope gate stands unused…

Monday checklist for locking down app connections

Start with what is already connected. Then prove on your own tenant that an unapproved app is refused before the connection exists, and don't rely on the vendor's description of it.

For a buyer who can't rely on a self-hosted install, this is the only evidence that counts.

Because each step produces a record the next one depends on, the list below runs in the order your approval chain will want to see it.

  1. List every connected app, with its owner and the data it touches.
  2. Decide the allow-list: which apps are permitted, and who signs off on additions.
  3. Ask the vendor for proof of enforcement in writing.
  4. Test a blocked app as a normal user.
  5. Re-check the pricing page before you sign and again at renewal.

Below, each step's failure mode is set out.

Inventory existing connections

Export the connection list from each platform your teams already use, and from the apps on the other side, because the platform's own list is often incomplete. Record the owner of every connection.

Draw up an allow-list without this inventory and it will either break live workflows or quietly exempt them; an auditor will ask which one happened. Then decide the allow-list and who approves exceptions.

Ask vendors to document app connection restrictions

Request three things, and accept any one of them if it's specific. They are the documentation page describing the admin control, the exact setting name and the plan it appears on, or the contract clause that commits the vendor to it.

A sales email saying the feature is "supported" isn't evidence.

Ask in the same message whether the control still applies on a self-hosted deployment, and get the answer in writing, since the previous section showed that this is where guarantees most often differ.

Test app connection blocking as a non-admin

Sign in as an ordinary user and try to connect an app that isn't on the list. The attempt should fail at the moment of connection, with no message that only appears after a scan.

If it succeeds and is flagged later, you have bought an audit, not a block. Keep the screenshot for the file.

Because plans and list prices change, re-check the pricing page on the day you sign and note which tier carries the control. Doing so also tells you whether a renewal quietly moves it.

Frequently asked questions

Can I block one app but allow the rest?

Only where the platform lets an administrator set a deny-list at workspace or organisation level, and that setting may sit on a higher plan than the one you are buying.

Set a deny-list and the named app can't be connected at all. It doesn't remove connections that already exist, so ask whether the setting acts on existing connections or only on new ones.

Then ask for the page in the vendor's own documentation that describes it. If the vendor can't point to one, treat the feature as unconfirmed.

Does self-hosting make restricting connections easier?

You get control of the network and the infrastructure from self-hosting, but not automatically an app-level control.

You can block outbound traffic to a domain at the firewall, which stops the connection working. That's a different thing from an admin setting that prevents the connection being created.

The first leaves the connection visible in the tool and failing. The second means it never appears.

Some platforms withhold their admin controls from the self-hosted edition or sell them under a separate licence. Check that the setting you were shown in the cloud product exists in the edition you'll run.

Is blocking apps the same as restricting credentials?

No. Blocking an app decides whether anyone in the workspace may connect to it. Restricting credentials decides who may use a connection once it exists: who can create it, who can reuse it in a workflow, and who can see the secret behind it.

You need both, and a vendor's answer to one question isn't an answer to the other. Ask for each control by name, and ask which role is allowed to change it.

How often do these plan limits change?

Because vendors revise plan names, tier contents and list prices on their own schedule, and most don't publish a changelog for what a tier includes, a feature that sits on one plan this year can move to another at renewal.

To make the vendor commit to it for the term, put the specific control in the order form or contract schedule. Then ask what notice the vendor owes you before moving it.

References

Share

Get started

Automate this without code.

Cloud or your own servers.

Start free Talk to sales