Can you use Make for custom API integrations?

Using Make for Custom API Integrations

Make (formerly Integromat) provides an HTTP module that connects to any API endpoint, extending its capabilities far beyond the 1,800+ pre-built app modules. As of April 2026, the HTTP module is available on all plans including the free tier.

HTTP Module Capabilities

Make a Request

• Methods: GET, POST, PUT, PATCH, DELETE
• Authentication: API key, Bearer token, OAuth 2.0, Basic auth, custom headers
• Body types: JSON, form data, raw, multipart (file uploads)
• Response parsing: Automatic JSON parsing with field mapping

Make an API Key Request

Simplified version for APIs requiring only an API key in headers or query parameters.

Make an OAuth 2.0 Request

Full OAuth 2.0 flow support with automatic token refresh.

Building a Custom API Integration

Step 1: Configure the HTTP Module

1. Add an HTTP "Make a request" module to the scenario
2. Enter the API endpoint URL
3. Set the method (GET, POST, etc.)
4. Add headers (Authorization, Content-Type)
5. Configure the request body if needed

Step 2: Parse the Response

Make automatically parses JSON responses. Map response fields to subsequent modules using the visual data mapping interface.

Step 3: Handle Pagination

For APIs that return paginated results, use Make's Repeater module or recursive scenarios to fetch all pages automatically.

Step 4: Error Handling

Add error handler modules to manage API rate limits (retry with delay), authentication failures (refresh token), and unexpected responses (log and alert).

Advanced API Features

• GraphQL: Send GraphQL queries and mutations via the HTTP module with JSON body
• SOAP/XML: Use the XML module to build and parse SOAP envelopes
• Webhooks: Create custom webhook endpoints in Make to receive data from any external system
• Client certificates: Attach TLS client certificates for mTLS-secured APIs

Practical Example: Custom CRM Sync

1. Trigger: New row in Google Sheets (incoming lead data)
2. HTTP module: POST to custom CRM API with lead data
3. Parse response: Extract the created contact ID
4. HTTP module: POST to Slack webhook with contact confirmation
5. Error handler: If CRM API returns 429 (rate limit), wait 60 seconds and retry

When to Use HTTP vs. Pre-Built Modules

• Use pre-built modules when available (they handle auth, pagination, and error codes automatically)
• Use HTTP modules for internal APIs, niche SaaS products, or when pre-built modules lack specific endpoints
• Consider the Make Custom App feature to package HTTP configurations as reusable modules shared across scenarios