Make.com HTTP Module

What the HTTP Module Does

The HTTP module in Make.com sends an HTTP request and receives the response. Configure:

• URL: The API endpoint
• Method: GET, POST, PUT, PATCH, DELETE
• Headers: Authorization headers, content-type, custom headers
• Query parameters: URL query string parameters
• Body: Request body (for POST/PUT/PATCH)
• Parse response: Whether to automatically parse JSON responses

The response is available to subsequent modules as structured data — if the response is JSON, all fields are accessible as mappable variables.

Common Authentication Patterns

API Key in header (most common):

or

API Key in query parameter: Some APIs (older pattern) accept the key as a URL parameter: https://api.service.com/endpoint?api_key=your-key

OAuth (already-connected apps): For services you've connected in Make.com's connection manager, use the OAuth connection rather than HTTP. Reserve HTTP for services that don't have Make.com connections.

Basic Auth: Username and password base64-encoded in the Authorization header. Most HTTP clients can generate this; alternatively, use the HTTP module's built-in Basic Auth option.

Making Claude API Calls

The HTTP module configuration for Anthropic's Claude API:

URL: https://api.anthropic.com/v1/messages Method: POST

Headers:

Body (JSON):

The response content[0].text contains Claude's output. Map this to subsequent modules.

Tip: Store your Anthropic API key in Make.com's data stores or as an environment variable to avoid embedding it directly in scenarios.

Parsing JSON Responses

When an API returns JSON, the HTTP module automatically parses it if you enable "Parse response." The parsed data becomes available as structured fields.

For nested JSON, use dot notation in mappings: {{4.body.contact.email}} — where 4 is the module number, body is the response body, contact is a nested object, and email is the field.

For arrays in the response, use the Iterator module (covered in the next section) to process each item.

When JSON parsing fails: Sometimes APIs return malformed JSON or the content-type header doesn't indicate JSON correctly. Use the JSON Parser module explicitly: pass the raw response text to the JSON Parser, which gives you structured data.

Handling Arrays in Responses

If an HTTP response contains an array (e.g., an API returns a list of contacts), use the Iterator module to process each item individually:

1. HTTP Request → fetch array response
2. Iterator module → "Array" field: map to the array in the response
3. Subsequent modules → process each item (these modules run once per array item)

Example: Fetch 50 contacts from a CRM API → Iterator → for each contact, enrich via another API and write to Airtable.

Rate Limiting and Retries

Most APIs have rate limits. The HTTP module handles this via error handling:

Configuring retries: Right-click the HTTP module → Add error handler → Resume → Set retry settings (number of retries, delay between retries). When the API returns a 429 (rate limit), the module retries after the delay.

Respecting rate limits proactively: Add a "Sleep" module after rapid API calls to introduce a delay. For example: after each API call, sleep 1 second to stay under 60 requests/minute.

Staggering requests: If processing many items, use the Iterator → HTTP module pattern with rate limiting built in. Make.com's execution model processes items sequentially, naturally throttling request rate.

Chaining Multiple API Calls

Many use cases require multiple API calls in sequence — fetch data from one API, transform it, send it to another. The HTTP module handles each call; map the output of one to the input of the next.

Example chain:

1. HTTP Request → Apollo: fetch company data by domain
2. HTTP Request → Claude: generate a summary using the Apollo data
3. HTTP Request → HubSpot: write the summary to the contact record

Each module's output is available to all subsequent modules. No additional configuration is needed to chain them.

Recommended Tools

• Make.com — HTTP module and scenario platform
• Claude API — AI capabilities via HTTP module
• OpenAI API — Also accessible via HTTP; native module also available
• Apollo.io — Enrichment data API
• HubSpot API — CRM data access beyond native module capabilities
• Postman — Test API calls before building in Make.com

“The HTTP module is what makes Make.com universal. Any service with an HTTP API integrates in minutes — no native module needed.”