Make (ex-Integromat): The Visual Automation Architecture Worth Understanding

Technical breakdown of Make — visual automation platform. Scenarios, routing, error handling, API integrations, scaling, and affiliate program.

Platform Architecture

Make (make.com, formerly Integromat) is a visual automation platform built around the concept of scenarios. Unlike Zapier with its linear “trigger → action” model, Make uses a directed graph: data flows through nodes, branches, transforms, and merges.

Make’s backend runs on Node.js with RabbitMQ-based queues. Each scenario compiles into a DAG (Directed Acyclic Graph), after which the scheduler distributes node execution across workers. This yields several architectural advantages over competitors.

Execution Model

A Make scenario is not just a sequence of steps. It’s a graph where each node receives a bundle from previous nodes and returns a new bundle or array of bundles:

Webhook → Router → [Branch A: HTTP → Filter → Email]
                 → [Branch B: Transform → Database → Slack]
                 → [Fallback: Log → Admin Alert]

The Router is the key feature. It doesn’t just pass data along — it spawns parallel execution branches. Each branch processes independently, enabling complex business logic without code.

Error Handling

Make provides four levels of error handling:

  1. Retry — automatic retry with exponential backoff (up to 5 attempts)
  2. Error handler route — dedicated scenario branch for errors
  3. Commit/Rollback — transactional model: all nodes succeed or rollback
  4. DLQ (Dead Letter Queue) — unhandled errors queue for manual review

Neither Zapier (only linear retries) nor n8n (has error branches but no transactions) offer this level.

API and Custom Integrations

Make supports 2000+ ready-made connectors, but the real power is in custom ones:

HTTP Module

Make requests to any API: REST, GraphQL, SOAP. Supports OAuth 2.0, API Keys, Basic Auth. Headers, query params, body — everything configured visually.

Webhooks

Inbound (receiving data from external services) and outbound (sending data). Support signature validation, IP filtering, custom responses.

Data Store

Key-value storage within Make. Persist state between scenario runs, aggregate data, maintain counters. Essentially serverless Redis without a server.

Custom Functions

When the visual editor falls short — JavaScript/TypeScript directly in the scenario. Access to fetch, lodash, moment.js.

Scaling

Tier Limit Description
Operations 10K–800K/month Each node = 1 operation
Scenario timeout 40 minutes Maximum single-run execution time
Data transfer 5–500 MB/run Data volume passing through the scenario

Pro plan scenarios run every minute (polling) or instantly (webhook). Enterprise: custom intervals and dedicated servers.

Security

  • All connections over HTTPS
  • OAuth 2.0 for connecting external services
  • Encryption in transit and at rest
  • RBAC (Role-Based Access Control) for teams
  • Full operation logging, including data (optional, for audit)
  • SOC 2 Type II, GDPR-compliant

Affiliate Program

Make offers 20% commission on each referral payment for 12 months. Platform: PartnerStack. Average customer spend: $16-34/month (Core and Pro tiers). One active referral yields $38-82/year. Payout threshold: $100.

Niche: business process automation, SaaS integrations, Zapier replacement.

Make Official Website EOF" 2>&1 | tail -3