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
- Add an HTTP "Make a request" module to the scenario
- Enter the API endpoint URL
- Set the method (GET, POST, etc.)
- Add headers (Authorization, Content-Type)
- 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
- Trigger: New row in Google Sheets (incoming lead data)
- HTTP module: POST to custom CRM API with lead data
- Parse response: Extract the created contact ID
- HTTP module: POST to Slack webhook with contact confirmation
- 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
Related Tools
Make
Automate your work with visual workflow builder and AI agents
Workflow AutomationZapier
Automate workflows between apps without coding—connect 9,000+ tools with simple, reliable automation.
Workflow Automationn8n
Workflow automation for technical teams
Workflow AutomationPipedream
Connect APIs, remarkably fast
Workflow AutomationRelated 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…
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…
Dive Deeper
Moxo vs Gumloop in 2026: Texting the Client, or Building the Agent
Gumloop (founded 2023) builds AI agents a company's own staff run; Moxo, whose predecessor Moxtra was co-founded in 2012, runs processes that wait on people outside the company. Gumloop wins three rounds to two: the way in, per-tool gating and a priced overage. Moxo wins on…
Moxo vs Relay.app in 2026: Where Relay's Approval Workflows Can Go Next
Relay.app, founded in 2021, shut down in September 2026 and deleted every account, workflow and run history; Moxo, whose predecessor Moxtra was co-founded in 2012, is one destination for its human-in-the-loop users. Relay.app takes two rounds, Moxo one, and vendor risk is a draw…
Moxo vs Workato in 2026: The Integration Estate, or the Approval Inside It
Workato, founded in 2013, is an enterprise integration platform whose Workflow apps add human tasks to recipes; Moxo, whose predecessor Moxtra was co-founded in 2012, ships the human step itself. Workato wins three rounds to two: connector reach, change control and the way in…