Access
Showcase

Try itExperimental
See what an agent can do with Make before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); the live MCP handshake runs real requests from our edge, right now — including, where the server allows it, one real read-only tool call (bring your own key for auth-gated servers); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://mcp.make.com/.well-known/oauth-protected-resourcerecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflowsevidence →
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Code extensibility — stories about code extensibility in this arenaCode extensibilityevidence →
Stories about code extensibility in this arena
Collaboration governance — stories about collaboration governance in this arenaCollaboration governanceevidence →
Stories about collaboration governance in this arena
Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystemevidence →
Stories about connectors ecosystem in this arena
Deployment embedding — stories about deployment embedding in this arenaDeployment embeddingevidence →
Stories about deployment embedding in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Reliability errors — stories about reliability errors in this arenaReliability errorsevidence →
Stories about reliability errors in this arena
Triggers scheduling — stories about triggers scheduling in this arenaTriggers schedulingevidence →
Stories about triggers scheduling in this arena
Visual builder — stories about visual builder in this arenaVisual builderevidence →
Stories about visual builder in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Make stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Official SDKs · Machine-readable spec · Versioning policy · API sandbox · Official CLI · Full data export · Drop into real code (JavaScript or Python) as a step inside a workflow · Connect to thousands of apps through prebuilt, vendor-maintained integrations · Start from a public library of workflow templates instead of building from scratch
Subscribe to events via webhooks
~6/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
~5/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~3/10
unlocks → MCP client · AI insights
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
✓8/10
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Code extensibility — stories about code extensibility in this arenaCode extensibility
Stories about code extensibility in this arena
Collaboration governance — stories about collaboration governance in this arenaCollaboration governance
Stories about collaboration governance in this arena
Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem
Stories about connectors ecosystem in this arena
Deployment embedding — stories about deployment embedding in this arenaDeployment embedding
Stories about deployment embedding in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Reliability errors — stories about reliability errors in this arenaReliability errors
Stories about reliability errors in this arena
Durability
Error handling
Inspect past execution logs and re-run a failed execution, resuming from the failing step
~4/10
Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling
Stories about triggers scheduling in this arena
Visual builder — stories about visual builder in this arenaVisual builder
Stories about visual builder in this arena
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payload G Triggers | developer | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 3 | full | 8/10 | Cclaimed | |
Expose my workflows or connected app actions as MCP tools that an external agent can call C Agent integration | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 3 | full | 8/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 7/10 | Cclaimed | |
Trigger workflows from events in connected apps (new record, message, email, form submission) C Triggers | ops user | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 3 | full | 7/10 | Cclaimed | |
Add AI agent or LLM steps inside a workflow, with model choice and tool use C Ai steps | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 3 | partial | 5/10 | Cclaimed | |
Build multi-step workflows in a visual editor without writing code C Builder | ops user | Visual builder — stories about visual builder in this arenaVisual builder | 3 | partial | 4/10 | Cclaimed | |
Configure automatic retries with backoff for failed steps or activities C Error handling | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 3 | partial | 3/10 | Cclaimed | |
Connect to thousands of apps through prebuilt, vendor-maintained integrations C Connectors | ops user | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 3 | none | 0/10 | ||
Store connection credentials centrally, share them with my team, and control who can use which credential C Credentials | ops user | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 3 | none | 0/10 | ||
Drop into real code (JavaScript or Python) as a step inside a workflow C Code steps | developer | Code extensibility — stories about code extensibility in this arenaCode extensibility | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Build a custom connector or private integration with a documented developer platform, SDK, or CLI G Connector dev | developer | Code extensibility — stories about code extensibility in this arenaCode extensibility | 2 | full | 7/10 | Tprobed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 7/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Map and transform data between steps with expressions, functions, or formulas C Data mapping | ops user | Code extensibility — stories about code extensibility in this arenaCode extensibility | 2 | partial | 6/10 | Cclaimed | |
Define dedicated error-handling paths or error workflows and get notified when a run fails C Error handling | ops user | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | partial | 5/10 | Cclaimed | |
Generate or edit a workflow from a natural-language prompt C Ai authoring | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | partial | 5/10 | Cclaimed | |
Have an agent create, update, and activate a workflow programmatically through the public API C Agent integration | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Compose reusable sub-workflows or modules that other workflows call C Composition | developer | Visual builder — stories about visual builder in this arenaVisual builder | 2 | partial | 4/10 | Cclaimed | |
Inspect past execution logs and re-run a failed execution, resuming from the failing step C Observability | ops user | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | partial | 4/10 | Cclaimed | |
Run workflows on cron-style schedules with timezone control C Schedules | ops user | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 2 | partial | 3/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Run long-lived workflows that wait for days and survive worker or platform restarts without losing state C Durability | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | none | 0/10 | ||
Test a workflow with sample or pinned data and inspect each step's input and output before going live C Testing | developer | Visual builder — stories about visual builder in this arenaVisual builder | 2 | none | 0/10 | ||
Version workflows through source control or environments and promote changes from dev to production C Versioning | developer | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 2 | none | 0/10 | ||
Branch a workflow with conditions, filters, and parallel paths that merge back together C Builder | ops user | Visual builder — stories about visual builder in this arenaVisual builder | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Pause a workflow to wait for human approval or input before it continues C Human in the loop | ops user | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Run workflows locally or against a dev instance for development and CI testing C Local dev | developer | Deployment embedding — stories about deployment embedding in this arenaDeployment embedding | 2 | none | untested | none yet | |
Start from a public library of workflow templates instead of building from scratch C Templates | ops user | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 5/10 | Cclaimed | |
Install community-built nodes, components, or integrations contributed outside the vendor C Community | developer | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 1 | partial | 4/10 | Cclaimed | |
Throttle or queue workflow executions to respect downstream rate limits C Durability | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 1 | partial | 4/10 | Cclaimed | |
Embed the automation platform white-label inside my own product for my customers C Embedding | developer | Deployment embedding — stories about deployment embedding in this arenaDeployment embedding | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 46 stories with headroom
What would move Make’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
All evidence describes Make exposing its own scenarios as an MCP server to external AI clients (Claude, ChatGPT), the reverse of this story's requirement that Make itself act as an MCP client consuming external MCP servers' tools.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq3/10moves Built-in AIimpact 31.5
Missing: detailed docs on the AI Agents app's task-delegation UX, concrete examples of use, and independent/hands-on corroboration of its capabilities.
Collaboration governance — stories about collaboration governance in this arenaStore connection credentials centrally, share them with my team, and control who can use which credential
nonemoves PA Scoreimpact 30
The evidence pack only lists 'Connections' as an app component category in custom-app developer docs (make-docs-10); there is no evidence describing centralized credential storage, team sharing, or per-credential access control for ops users.
Code extensibility — stories about code extensibility in this arenaDrop into real code (JavaScript or Python) as a step inside a workflow
nonemoves PA Scoreimpact 30
The evidence pack covers Make's API, webhooks, MCP server, error handling, and functions, but contains no mention of a custom code step, JavaScript/Python module, or code-execution capability inside a Make scenario.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: documented data export/download feature, open format (e.g., JSON/CSV) export of scenarios and data stores, any GDPR-style account export or migration tooling.
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Connectors ecosystem — stories about connectors ecosystem in this arenaConnect to thousands of apps through prebuilt, vendor-maintained integrations
nonemoves PA Scoreimpact 30
Missing: any documentation or listing of the app/connector marketplace, connector count, or vendor-maintenance claims.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
The evidence pack contains no mention of AI training data opt-out, data usage policies for AI model training, or any privacy controls addressing this specific concern; all evidence covers API auth, MCP server, webhooks, and error handling instead.
Showing the top 8 of 46 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map10 surfaces · 30 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
MCP server docs12 stories
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Have an agent create, update, and activate a workflow programmatically through the public API
- Expose my workflows or connected app actions as MCP tools that an external agent can call
- Generate or edit a workflow from a natural-language prompt
- Add AI agent or LLM steps inside a workflow, with model choice and tool use
- Perform bulk operations across many items at once
- Do everything through the API that I can do in the UI
Webhooks docs12 stories
- Run the product headlessly / in CI for automation
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Throttle or queue workflow executions to respect downstream rate limits
- Run workflows on cron-style schedules with timezone control
- Trigger workflows from events in connected apps (new record, message, email, form submission)
- Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payload
- Build multi-step workflows in a visual editor without writing code
- Compose reusable sub-workflows or modules that other workflows call
API documentation docs8 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Have an agent create, update, and activate a workflow programmatically through the public API
- Perform bulk operations across many items at once
- Build a custom connector or private integration with a documented developer platform, SDK, or CLI
- Do everything through the API that I can do in the UI
Error handling docs6 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Configure automatic retries with backoff for failed steps or activities
- Define dedicated error-handling paths or error workflows and get notified when a run fails
- Inspect past execution logs and re-run a failed execution, resuming from the failing step
- Build multi-step workflows in a visual editor without writing code
Scenarios and connections docs6 stories
- Set up automations that run autonomously in the background
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Inspect past execution logs and re-run a failed execution, resuming from the failing step
- Run workflows on cron-style schedules with timezone control
- Build multi-step workflows in a visual editor without writing code
OpenAPI spec4 stories
Custom apps documentation docs4 stories
- Build a custom connector or private integration with a documented developer platform, SDK, or CLI
- Install community-built nodes, components, or integrations contributed outside the vendor
- Trigger workflows from events in connected apps (new record, message, email, form submission)
- Compose reusable sub-workflows or modules that other workflows call
Make AI agents docs4 stories
Functions docs3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://mcp.make.com/.well-known/oauth-protected-resourcereproduced$ curl -s https://mcp.make.com/.well-known/oauth-protected-resource
{"resource":"https://mcp.make.com/","authorization_servers":["https://www.make.com/mcp"],"bearer_methods_supported":["header"]}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 14 testable claims verified · 0 contradicted → integrity 43/100
18 distinct capability claims found in Make’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
8
Unverified
0
Contradicted
16
Undersold
Verified (7)
“Active and on-demand scenarios can be turned into callable tools for AI systems”
Expose my workflows or connected app actions as MCP tools that an external agent can callfullproof ↗
“Make MCP server lets AI systems like Claude and ChatGPT act as MCP clients to run and manage scenarios”
“Make Skills are markdown files that help an AI assistant build scenarios, configure modules, and connect to Make MCP server or third-party services”
Point an agent at llms.txt or agent-oriented docsfullproof ↗
“Custom apps can be built from components: base, connections, webhooks, modules, and remote procedure calls”
Build a custom connector or private integration with a documented developer platform, SDK, or CLIfullproof ↗
“Make API follows REST design with resource-oriented URLs”
Drive the product through a documented public APIfullproof ↗
“API lets you view and modify scenarios and related entities like connections, webhooks, and data stores”
Do everything through the API that I can do in the UIpartialproof ↗
“Make MCP server allows LLMs to run scenarios and manage the contents of a Make account”
Unverified (9)
“Custom webhooks let you create a URL to receive any data sent from an external app or service”
Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payloadfullproof ↗
“Webhook-triggered scenarios can be scheduled to process queued requests periodically instead of running immediately”
Run workflows on cron-style schedules with timezone controlpartialproof ↗
“Docs provide detailed guidance on common errors, warnings, and error handlers for diagnosing scenario issues”
Define dedicated error-handling paths or error workflows and get notified when a run failspartialproof ↗
“Built-in functions let you transform and format data within scenarios”
Map and transform data between steps with expressions, functions, or formulaspartialproof ↗
“Make AI Agents app supports agentic automation”
Add AI agent or LLM steps inside a workflow, with model choice and tool usepartialproof ↗
“API requests require authentication via a user token with configurable scopes”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
“Scenario history is available for reviewing past runs”
Inspect past execution logs and re-run a failed execution, resuming from the failing steppartialproof ↗
“Webhook queue is fully processed each time the scenario's schedule criteria are met”
Run workflows on cron-style schedules with timezone controlpartialproof ↗
“Scenarios can be scheduled, cloned, and deleted via documented operations”
Undersold (16)
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Have an agent create, update, and activate a workflow programmatically through the public APIpartialproof ↗
Generate or edit a workflow from a natural-language promptpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventsfullproof ↗
Install community-built nodes, components, or integrations contributed outside the vendorpartialproof ↗
Throttle or queue workflow executions to respect downstream rate limitspartialproof ↗
Configure automatic retries with backoff for failed steps or activitiespartialproof ↗
Trigger workflows from events in connected apps (new record, message, email, form submission)fullproof ↗
Build multi-step workflows in a visual editor without writing codepartialproof ↗
Compose reusable sub-workflows or modules that other workflows callpartialproof ↗
Claims outside our story set (2)
Real capability claims found in Make’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Scenarios can be cloned”
source ↗“Dedicated troubleshooting section covers what can go wrong with the API and how to fix it”
source ↗
Business model
Free tier with limited operations; paid plans charge a monthly fee metered by operations volume, scaling up through Teams to custom-priced Enterprise.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP 100% · llms.txt 100% (30d, checked every 6h since Sep 8 '26)
