# Make Integration - Build Visual API Workflows

> Step-by-step guide to using APIVerve with Make (formerly Integromat). Build complex automation scenarios with visual workflows.

# Make Integration

Build complex automation scenarios with Make's visual workflow builder. Our native integration provides dynamic inputs for all APIs with support for advanced routing and error handling.

![Make](https://apiverve.web.app/integrations/logos/make.png)

[View on Make](https://www.make.com/en/integrations/apiverve)

## What is the Make Integration?

Make (formerly Integromat) is a powerful visual automation platform that lets you design complex workflows with branching logic, error handling, and data transformation. Our native Make integration brings all 100+ APIVerve APIs directly into your scenarios.

Like our other native integrations, Make features **dynamic inputs** - select any API and the module automatically displays the correct input fields. This makes it easy to switch between APIs or use multiple APIs in the same scenario without any manual configuration.

Make excels at complex workflows. Use routers to create conditional branches based on API responses, iterators to process arrays of data, and aggregators to combine results. The visual canvas makes it easy to understand and debug your automations.

**Plan Requirement**

The Make integration requires a paid APIVerve plan (Starter, Pro, or Mega). Free accounts have limited access for testing purposes.

## Before You Start

To use APIVerve with Make, you'll need:

-   An APIVerve account with an active subscription (Starter, Pro, or Mega)
-   A Make account (free tier available with limits)

## Connecting APIVerve to Make

Make uses a visual canvas where you drag and connect modules. Setting up APIVerve is straightforward - create a connection once and reuse it across all your scenarios.

### Step 1: Create a New Scenario

Log into Make and click "Create a new scenario". You'll see a blank canvas with a starting circle where you'll add your first module.

### Step 2: Add Your Trigger

Click the starting circle and choose your trigger module. Make offers webhooks for real-time data, scheduled triggers for time-based automation, and app-specific triggers like "Watch Rows" in Google Sheets.

### Step 3: Add the APIVerve Module

Click the "+" icon after your trigger to add a new module. Search for "APIVerve" and select it. You'll be prompted to create a connection to your APIVerve account.

### Step 4: Sign In with OAuth

Click "Add" next to the Connection field, then click "Save". You'll be redirected to APIVerve's login page where you can sign in with your account credentials. After authorizing the connection, Make will securely link to your account.

**Reusable Connections**

Once you create a connection, it's saved to your Make account. You can select it in any scenario without re-authenticating. Revoke access anytime from your APIVerve dashboard.

### Step 5: Configure the API Call

Select the API you want to use from the dropdown menu. Make will automatically load the available parameters for that API. Map data from previous modules using Make's mapping panel - click any field and select variables from your trigger or other modules.

### Step 6: Test and Activate

Click "Run once" to test your scenario with real data. Make will execute each module in sequence and show you the output at every step. When everything works correctly, toggle the scenario "ON" to activate it.

## Make-Specific Features

Make offers several powerful features that work great with API workflows:

### Routers for Conditional Logic

Add a router after an APIVerve module to create multiple paths based on the API response. For example, after validating an email, route valid emails to one path and invalid emails to another. Each path can have its own filter conditions and subsequent actions.

### Error Handling

Make provides robust error handling options. You can configure each module to ignore errors and continue, break execution and retry later, rollback previous actions, or trigger a specific error handler route. This is essential for production workflows where API calls might occasionally fail.

### Iterators and Aggregators

Need to process multiple items? Use an iterator to break an array into individual items, process each one with APIVerve, then use an aggregator to combine the results back together. This is perfect for batch operations like validating a list of emails from a spreadsheet.

## Popular Use Cases

### Batch Processing Pipeline

Process large datasets efficiently. Trigger on a schedule, fetch rows from Google Sheets, iterate through each row, call the appropriate APIVerve API, then update the sheet with results. Make's execution history makes it easy to track progress and identify issues.

### Multi-API Workflows

Chain multiple APIs together in a single scenario. For example: receive a URL via webhook, generate a screenshot with the Screenshot API, extract text from the image with OCR, analyze sentiment, then store everything in your database. Make's visual canvas makes these complex flows easy to understand.

### Conditional Data Routing

Route data based on API responses. After checking if an email is valid, route valid business emails to Salesforce, valid personal emails to Mailchimp, and invalid emails to a review queue. Make's routers and filters make this kind of logic straightforward.

## Tips for Success

-   **Use the execution history** - Make logs every execution with full details, making debugging easy
-   **Add error handlers** - Configure error handling for API modules to prevent scenario failures
-   **Set up scenarios in folders** - Organize related scenarios together for easier management
-   **Use data stores** - Make's built-in data stores are great for caching API results
-   **Schedule wisely** - Balance frequency with your API token allocation

## Troubleshooting

### Connection Issues

If you can't connect your account, verify your API key is correct with no extra spaces or line breaks. Check that your APIVerve subscription is active. If problems persist, try deleting the connection and creating a new one.

### Module Errors

Open the execution log to see detailed error messages. Common issues include missing required fields, incorrect data types, or token exhaustion. Make shows exactly what data was sent and received at each step.

### Rate Limiting

For high-volume scenarios, use Make's built-in rate limiting. Add a sleep module between iterations or configure the scenario's execution limit. Consider upgrading your APIVerve plan if you consistently need higher throughput.

## Additional Resources

-   [APIVerve on Make](https://www.make.com/en/integrations/apiverve) - Install the integration
-   [Integration Overview](https://apiverve.com/integrations/make) - More details on the main site
-   [API Reference](/api-endpoints) - Explore all available APIs
-   [Rate Limits](/rate-limits) - Understand usage limits by plan

Help us improve our documentation

YesNo

Copy for LLM[View as Markdown](/integrations/make/ai.md "View this page as plain markdown")

---

*Source: [docs.apiverve.com/integrations/make](https://docs.apiverve.com/integrations/make)*