Migrating from Make (Integromat)

Make (formerly Integromat) is a visual automation platform known for its canvas-based scenario builder and powerful data manipulation tools. This guide explains how Make concepts translate to Chase Agents and how to migrate your scenarios.

Concept Mapping

A Make Scenario maps to a Chase Agents Automation. Make's modules (trigger modules, action modules, and tool modules) map to Chase Agents' step types. Make's routers (which split execution into parallel paths based on conditions) map to Chase Agents' if and switch steps, which support branching. Make's Aggregator module (which combines data from multiple iterations) is similar to Chase Agents' merge step. Make's Iterator module maps to Chase Agents' loop step.

What You Gain

Chase Agents adds AI-native capabilities that Make does not offer natively. The run_sandboxed_code step gives you full Python execution, which is more powerful than Make's built-in data manipulation functions. The ability to call any MCP-compatible service means you are not limited to Make's app catalog. Human approval steps and self-healing auto-fix capabilities make Chase Agents better suited for production-critical automations.

Handling Make's Operations Model

Make charges by operations (each module execution counts as an operation). Chase Agents charges by actions (tool executions through MCP connections). The billing models are similar in spirit but the unit costs and included quotas differ. When evaluating your migration economics, count how many MCP connection tool calls your equivalent Chase Agents automation would make per run and multiply by your expected run frequency to estimate action consumption.

Migration Approach

Export or document your Make scenarios before starting the migration. For each scenario, note the trigger type, the sequence of modules, any routers and their filter conditions, and the data fields being passed between modules. This documentation becomes the specification you use when describing the automation to the Chase Agents chat builder.

Replicating Make's Error Handling

Make has a built-in error handler mechanism that lets you define fallback routes when a module fails. In Chase Agents, error handling is managed through the automation's error handling mode (ai or any). For scenarios where you want explicit error routing similar to Make's error handlers, use the any error mode and configure notifications, then build a separate automation that detects failed runs and takes recovery actions.

Make's Built-In Apps

Make includes a large catalog of pre-built app connections. Chase Agents uses the MCP ecosystem, which is growing rapidly. For apps not yet available as native MCP servers, use the Custom Connectors feature to add them via their REST API. Many services have publicly documented APIs that can be connected in minutes using the custom connector approach.

Testing Your Migration

Run both the Make scenario and the Chase Agents automation against the same test data and compare outputs before cutting over. For complex scenarios that transform data through multiple steps, verify the intermediate values at each step using Chase Agents' Workflow History step-level detail view. Once outputs match, disable the Make scenario and enable the Chase Agents automation as the primary.

Getting Help

For complex Make scenarios that are difficult to migrate, share the details in the Chase Agents Discord community. Describe the scenario's purpose, the modules it uses, and where you are getting stuck. The team and community can advise on the best Chase Agents approach.