Where the reviewed products stand
Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).
0–10 on both axes · Higher and further right means more documented control
Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗
Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗
Workflow definitions depend on their runtime, connectors and credentials. Definition export does not establish portable execution history or an independent runtime.
Compare the six dimensions
| Overall control | |
|---|---|
| Data access | |
| Third-party accessibility | |
| External action | |
| Continuity | |
| Data exit | |
| Business logic and customization | |
Product scopes, dates & reviews
Make
Workflow automation · Checked 2026-10-22
Make / scenario collection, scenario creation/update and scoped API-token access; connection secrets, execution-data completeness and independent execution are excluded.
Read findings and sources ↗n8n
Workflow automation · Checked 2026-10-22
n8n / public API workflow definitions and workflow mutations; credentials, execution histories, hosting licenses and complete instance migration are excluded.
Read findings and sources ↗| Customer control | Make ↗ | n8n ↗ | Zapier ↗ | Permute ↗ |
|---|---|---|---|---|
| Category | Workflow automation | Workflow automation | Workflow automation | Databases and data platforms |
| Overall control | ||||
| Data access | ||||
| Third-party accessibility | ||||
| External action | ||||
| Continuity | ||||
| Data exit | ||||
| Business logic and customization | ||||
| Assessment scope | Make / scenario collection, scenario creation/update and scoped API-token access; connection secrets, execution-data completeness and independent execution are excluded. | n8n / public API workflow definitions and workflow mutations; credentials, execution histories, hosting licenses and complete instance migration are excluded. | Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. | Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. |
| Assessment checked | 2026-10-22 | 2026-10-22 | 2026-10-22 | 2026-10-12 |
| Read the findings | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ |
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
Who can connect?
Yes No- Unknown
| Connection method | Customer credentials | Integrator credentials | Provider approval required |
|---|---|---|---|
| Make ↗ | |||
| scenario collection, scenario creation/update and scoped API-token access ↗ | |||
| n8n ↗ | |||
| public API workflow definitions and workflow mutations ↗ | |||
| Zapier ↗ | |||
| Workflow API v2 Zap enumeration for an embedded public integration ↗ | - | - | |
| Permute ↗ | |||
| Scoped customer REST / TypeScript SDK ↗ | |||
| Permissioned end-user MCP ↗ | |||
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
What each review covers
Make ↗
Make exposes scenario metadata and operations through its API. An organization’s role and the token’s scopes constrain access.
Make / scenario collection, scenario creation/update and scoped API-token access; connection secrets, execution-data completeness and independent execution are excluded.
n8n ↗
n8n’s public API exposes workflow definitions within the key’s permissions. Workflow JSON export is separate from credentials and execution history.
n8n / public API workflow definitions and workflow mutations; credentials, execution histories, hosting licenses and complete instance migration are excluded.
Zapier ↗
Zapier’s Workflow API lists user-owned Zaps. Default results contain the authenticating integration; broader scopes are needed for other or shared workflows.
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Permute ↗
Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.