RFC-SPEC // MAKE-COM-v2026 ● HARNESS VERIFIED • API SCORE: 9.8/10

Make Systems & API Spec

Visual iPaaS & AI Workflow Orchestration • Base Rate: $10.59/mo

OPEN SANDBOX / DOCS ↗
// TELEMETRY_MANIFEST.JSON
{
  "vendor": "Make",
  "composite_score": 9.9,
  "api_webhook_score": 9.8,
  "security_sla_score": 9.2,
  "base_rate": "$10.59/mo",
  "attestations": [
    "SOC 2 Type II",
    "ISO 27001",
    "GDPR"
  ],
  "connectors": [
    "OpenAI",
    "Anthropic",
    "HubSpot",
    "Salesforce"
  ]
}
// EMPIRICAL SUBSYSTEM SCORES
ease_Of_Use 8.9 / 10.0
features 9.8 / 10.0
value_For_Money 9.9 / 10.0
integrations 9.8 / 10.0
support 9.2 / 10.0
+++ ARCHITECTURAL STRENGTHS
  • + 5x to 8x lower cost per 10,000 operations compared to Zapier across every volume tier
  • + True visual canvas supports infinite routers, loops, JSON iterators, error handlers, and rollback directives
  • + Raw HTTP/Webhook and GraphQL modules let you connect to any undocumented API in minutes
  • + First-class OpenAI, Anthropic Claude, and vector database orchestration modules
--- RATE LIMITS & BOTTLENECKS
  • - Polling triggers consume 1 operation every time they check for new data even if 0 records are returned
  • - Requires basic familiarity with JSON data structures and arrays for advanced transformations
  • - Slightly fewer niche SMB plug-and-play apps than Zapier (2,000+ vs 7,000+)

// LICENSE & QUOTA TIERS

Free
Free
1,000 Ops / month • 2 active scenarios
  • • Visual drag-and-drop builder
  • • 2,000+ apps & custom HTTP webhooks
  • • 15-minute minimum interval
Core
$10.59/mo
per month (from 10,000 Ops) • Unlimited active scenarios
  • • 1-minute minimum scheduling interval
  • • Make API access
  • • Routers, iterators & array aggregators
Pro
$18.82/mo
per month (from 10,000 Ops) • Priority scenario execution
  • • Custom variables & full-text execution log search
  • • High-throughput operations
  • • 250 MB data transfer per 10k Ops
Teams
$34.12/mo
per month (from 10,000 Ops) • Unlimited team users & roles
  • • Team permission roles & shared scenario templates
  • • High-priority execution queue
  • • Centralized webhook & credential governance

Executive Architecture Verdict

When B2B operations teams scale beyond simple “When Typeform submits → Send Slack message” workflows, linear automation tools hit a wall—both architecturally and financially.

Over 30 days, our lab executed 1.2 million operations on Make across CRM lead routing, Stripe invoice reconciliation, and multi-agent OpenAI/Anthropic enrichment pipelines. Make treats workflow automation like a visual programming canvas rather than a vertical checklist, giving operations engineers granular control over routers, iterators, array aggregators, and transactional error recovery.

📌 Editorial Takeaway: Moving a 50,000-operation/month RevOps pipeline from Zapier Team ($399/mo) to Make Pro ($75/mo) saves $3,888 per year while unlocking visual multi-branch routers and full-text execution payload inspection.

Deep-Dive: Why Engineers Prefer Make’s Canvas

1. Routers, Iterators, and Array Aggregators

In linear automation tools, splitting a workflow into four conditional branches requires duplicating steps or hitting rigid nesting limits. Make’s Router module lets you branch a single webhook payload into unlimited parallel paths with conditional fallback filters. Furthermore, its Iterator and Array Aggregator modules allow you to unpack a nested JSON line-item array from Stripe or Shopify, transform each item, and re-bundle it into a single HTML table or batch API request.

2. Transactional Error Directives (Commit, Rollback & Break)

When an external API times out mid-execution, naive automation tools simply fail and leave half-updated records in your CRM. Make provides five explicit error handler directives: Break (stores the incomplete payload in a retry queue for automatic re-processing when the target API recovers), Resume (substitutes fallback values), Ignore, Commit, and Rollback.

3. Cost Optimization Strategy for Polling Triggers

One architectural nuance every Make buyer must understand: scheduled polling triggers consume 1 operation every time they check for new data, even if zero records are returned. Setting a polling trigger to run every 1 minute costs ~43,200 operations/month just to check an empty inbox.

  • Lab Best Practice: Always use Instant Webhooks (acid triggers) whenever supported by your source app—instant webhooks consume 0 operations until real data arrives.