Make

Make (formerly Integromat) provides visual workflow automation with more sophisticated logic than Zapier: branching (routers), loops (iterators/aggregators), error handling paths, and data transformation functions. For agents, Scenarios (Make's workflow unit) can implement complex multi-step processes with conditional logic, parallel execution, and data manipulation. The HTTP module enables arbitrary API calls within scenarios — agents can call any REST API as a scenario step. Webhook triggers accept incoming HTTP requests. The API enables programmatic scenario management: create, update, run, and monitor scenarios. For agents needing automation with complex logic (data transformation, conditional routing, error recovery), Make provides capabilities that Zapier's linear Zaps can't match. The visual builder is powerful but scenario complexity can grow quickly.

API token authentication via Authorization: Token header. Tokens are generated in the Make account settings. No fine-grained token scoping — tokens grant full account access. Webhook endpoints use unique URLs as credentials (similar to Zapier). Scenario connections store credentials for integrated apps securely. OAuth and API key auth for connected app integrations. For agents, the API token provides full account management access. Webhook URLs should be treated as secrets. No IP restrictions on API tokens. The auth model is simple. The main security consideration: scenarios can store and use sensitive credentials for connected apps — account access implies credential access.

Documentation covers the visual builder, app integrations, API reference, and scenario design patterns. The API reference documents scenario management, webhook, connection, and data store endpoints. The visual builder documentation covers modules, routers, iterators, and error handling with visual examples. App integration documentation covers each connected service. Community resources include a forum and template gallery. The documentation is adequate but the API reference is less polished than the visual builder documentation — Make prioritizes the visual builder experience. For agents using the API, the scenario management and webhook endpoint documentation are the key resources. SDK: no official SDKs — agents use raw HTTP.

REST API at eu1.make.com/api/v2/ (or other regions). Scenario management: GET /scenarios lists scenarios, POST /scenarios creates, PATCH updates, POST /scenarios/{id}/run triggers execution. Webhook management: POST /hooks creates webhook endpoints. Scenario blueprint export/import enables version control. Connection management provides API credential storage for scenario steps. Data store management handles persistent key-value storage. The API enables full scenario lifecycle management — agents can programmatically create, modify, and execute automation workflows. Webhook triggers accept HTTP POST/GET with arbitrary payloads. The API for scenario management is more comprehensive than Zapier's. Execution history: GET /scenarios/{id}/logs provides run history with step-level detail.

API errors return JSON with message and detail. Scenario execution errors are logged per-module (step) with error type, message, and data. Error handling routes in scenarios enable recovery logic: retry, ignore, commit, rollback, and break. This is significantly more sophisticated than Zapier's error handling. Execution history retains input/output for each module. Incomplete executions (partial failures) can be replayed. Rate limits on the API are per-account. Operations quota limits scenario execution volume per plan. The main reliability consideration: complex scenarios with many modules and branches can be difficult to debug — the execution log is essential. For agents, monitoring the execution API for failed runs enables proactive error handling.