Can you use Make for custom API integrations?

Quick Answer: Yes. Make's HTTP module sends requests to any REST API, and its JSON module parses responses. Teams can connect to APIs without pre-built integrations by configuring HTTP method, headers, authentication, and body. Make also supports GraphQL, SOAP, and webhook-based APIs.

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 3,000+ pre-built apps (mid-2026). 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

Related Questions

Written & reviewed by Rafal Fila · Last updated:

Related Tools

Make

Automate your work with visual workflow builder and AI agents

Workflow Automation

Zapier

Automate workflows between apps without coding—connect 9,000+ tools with simple, reliable automation.

Workflow Automation

n8n

Workflow automation for technical teams

Workflow Automation

Pipedream

Connect APIs, remarkably fast

Workflow Automation

Related Rankings

Best Human-in-the-Loop Automation Platforms 2026

Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.

Best Automation Platforms for AI Orchestration 2026

This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.

Dive Deeper

comparison

Moxo vs Lindy in 2026: Who Presses Approve When the Agent Asks

Lindy, founded in 2023, sells an AI teammate that lives in Slack and in each person's inbox; Moxo, whose predecessor Moxtra was co-founded in 2012, runs multi-party processes where approvals are steps only a person can close. Moxo wins three rounds to two: who closes the step, work across companies and the record. Lindy wins reach and testing. Vendor pages and docs read 28 September 2026.

comparison

Moxo vs Kissflow in 2026: What an Outside Approver Costs, and What the Record Proves

Moxo and Kissflow both sell approvals to people who do not write code, and each wins one round outright: Moxo's Web and Headless SDKs run the approval inside the buyer's own product, under the buyer's own sign-in. Kissflow's portal audit log stamps every event with an actor, a device and an IP, where Moxo publishes no field list. Both answers are quoted, not priced, and both meters punish a one-step request sent to hundreds of clients. Cost, the decision record, rejection routes, AI metering and governance, verified 14 to 23 September 2026.

comparison

Moxo vs Camunda 8 in 2026: BPMN User Tasks for Staff, Step Types for Outsiders

Camunda 8 can fix a process under cases already running, since active instances migrate onto a corrected definition and, for Camunda user tasks, "a migrated active user task remains assigned to the same user". Moxo keeps the shared queue that Camunda's Tasklist V2 stops evaluating, with desks that are "a shared inbox that multiple users can pick work from". Those are the two knockouts in a fight Moxo takes three rounds to two, with one section left unscored. Portability, AI review gates and a published price decide the rest, verified 14 to 23 September 2026.