Make (Integromat)

Node-based workflow editor enabling users to construct automation sequences by dragging pre-built modules (triggers, actions, conditionals) onto a canvas and connecting them with visual edges. The builder renders a real-time directed acyclic graph (DAG) representation of the workflow, with each node encapsulating a specific action (API call, data transformation, conditional branch) and edges defining execution flow. The platform abstracts underlying API complexity through a visual interface, translating node configurations into orchestration instructions executed by the backend engine.

Backend orchestration system that executes scenarios based on trigger events (webhook, schedule, manual), routes execution through action nodes, and applies conditional branching logic to determine flow paths. The engine manages state across multi-step workflows, handles inter-service communication, and provides real-time visibility into execution progress via a monitoring dashboard showing active runs, execution logs, and error states. Execution model (at-least-once vs exactly-once semantics) is undocumented, but the platform supports branching logic and conditional routing typical of enterprise iPaaS systems.

Collection of pre-built scenario templates covering common automation patterns (lead qualification, customer onboarding, data synchronization, report generation). Templates provide starting points for users, reducing time-to-automation by eliminating the need to build workflows from scratch. Templates are customizable through the visual builder; users modify trigger conditions, app selections, and data mappings to fit their specific use case. The platform also enables users to save custom scenarios as reusable templates for team sharing.

Make offers a free tier enabling users to build and execute unlimited workflows without providing a credit card or payment information. The free tier includes access to the visual builder, all 3,000+ connectors, and unlimited scenario executions (subject to fair-use policies). Limitations on the free tier are not documented but typically include reduced API rate limits, limited team members, or reduced execution priority compared to paid tiers. The free tier enables users to prototype and learn Make before committing to paid plans.

Capability enabling workflows to handle errors gracefully through conditional branching based on error types or execution outcomes. Users configure error handlers (alternative paths) that execute when a node fails, enabling workflows to retry, skip, or take corrective action. Conditional branching supports decision logic based on previous node outputs, enabling workflows to route around failures or implement fallback logic. Specific error handling mechanisms (automatic retries, exponential backoff, dead-letter queues) are not documented.

Curated collection of pre-configured API connectors abstracting authentication, request/response formatting, and error handling for 3,000+ SaaS applications and services. Each connector encapsulates service-specific logic (OAuth flows, API versioning, rate limit handling) and exposes a simplified action interface (e.g., 'Create HubSpot Contact', 'Send Slack Message') that users select in the visual builder. Connectors handle credential management, payload transformation, and service-specific quirks, eliminating the need for users to write raw API calls or manage authentication tokens.

Built-in modules enabling workflows to invoke AI services (OpenAI's ChatGPT, DALL-E, Whisper; Perplexity AI; DeepSeek) directly within scenario execution. Users configure AI modules by selecting the service, model, and input parameters (prompt, image URL, audio file) in the visual builder; the platform handles API calls, credential management, and response parsing. AI outputs (text, images, transcriptions) are passed to downstream workflow nodes for further processing or delivery to end users.

Framework enabling users to define autonomous agents that can decompose tasks, make decisions, and orchestrate multi-step workflows without explicit step-by-step configuration. Agents leverage AI reasoning to determine next actions based on task context and available tools (integrated services). The platform provides pre-built agent examples and templates, reducing setup time. Agents operate within the Make execution engine, accessing the same 3,000+ connectors and monitoring infrastructure as manual workflows.

Mechanism enabling external systems to trigger Make workflows via HTTP webhooks. Users generate unique webhook URLs for each scenario; external applications POST event data to these URLs, which invoke the scenario and pass the payload as input to the first workflow node. Webhooks enable event-driven automation (e.g., 'trigger workflow when GitHub PR is created') without polling or scheduled checks. Webhook payload validation, authentication, and rate limiting are handled by the Make platform.

Capability enabling workflows to execute on a schedule (cron-like expressions) or at fixed intervals (hourly, daily, weekly, monthly). Users configure trigger timing in the visual builder; the Make scheduler invokes scenarios at specified times without requiring external cron services or scheduling infrastructure. Scheduled workflows execute asynchronously and are subject to the same execution engine and monitoring as event-triggered workflows.

System enabling users to map and transform data flowing between workflow nodes without writing code. Users select source fields from previous nodes and map them to target fields in downstream nodes; the platform supports basic transformations (string concatenation, date formatting, arithmetic) through a visual interface. Complex transformations may require custom code or external services (unknown if Make supports JavaScript/Python execution for advanced transformations).

Features enabling teams to collaborate on workflow design, execution, and monitoring within an enterprise environment. The platform supports role-based access control (RBAC), team workspaces, shared scenario libraries, and centralized monitoring dashboards. Enterprise tier includes SSO (Single Sign-On) for authentication, audit logging, and dedicated support. Multiple team members can view, edit, and execute workflows with granular permission controls.

Dashboard providing real-time visibility into active and historical workflow executions. The monitoring interface displays a visual workflow map with execution state (running, completed, failed) for each node, execution logs showing inputs/outputs per node, error messages, and performance metrics (duration, API calls). Users can inspect individual executions to debug failures, understand data flow, and optimize performance. Monitoring data is retained for historical analysis (retention period unknown).