Make.com AI Humanizer: HumanTone HTTP Module Configs

Overview

Make's built-in HTTP > Make a request module calls every HumanTone humanizer endpoint. The blueprints below import as fully wired modules on Make.com. Same API, same credits, same response shapes as the HumanTone API reference.

Note: The HTTP module does not store credentials globally in Make. Your API key lives in the module's Authorization header. If you build several scenarios with HumanTone, paste the same Bearer token into each module's Authorization field, or store it once in a Make data store and reference it across scenarios.

Setup

1
Get an API key at app.humantone.io/settings/api. Requires a paid HumanTone plan.
2
In Make, open any scenario canvas. Right-click the canvas and choose Import blueprint, or use the keyboard shortcut and paste one of the JSON blueprints below.
3
After import, click the new HTTP module, find the Authorization header, and replace ht_your_api_key with your real API key.

Humanize

POST /v1/humanize

Rewrites AI text to sound natural. Returns the humanized content plus credits used and a request ID.

json

{
  "subflows": [
    {
      "flow": [
        {
          "id": 1,
          "module": "http:MakeRequest",
          "version": 4,
          "parameters": {
            "authenticationType": "noAuth"
          },
          "mapper": {
            "url": "https://api.humantone.io/v1/humanize",
            "method": "post",
            "headers": [
              {
                "name": "Authorization",
                "value": "Bearer ht_your_api_key"
              }
            ],
            "contentType": "json",
            "inputMethod": "jsonString",
            "jsonStringBodyContent": "{\n  \"content\": \"\",\n  \"custom_instructions\": \"\",\n  \"humanization_level\": \"standard\",\n  \"output_format\": \"text\"\n}",
            "parseResponse": true
          },
          "metadata": {
            "designer": {
              "x": 0,
              "y": 0
            }
          }
        }
      ]
    }
  ],
  "metadata": {
    "version": 1
  }
}

Body fields to configure

Field	Required	Notes
content	Yes	The text to humanize. Map from a previous module, e.g. `{{1.text}}`. Minimum 30 words.
humanization_level	No	`standard` (default), `advanced`, or `extreme`. Advanced and Extreme are English only.
output_format	No	`text`, `html`, or `markdown`. Defaults to `html` in the API. The imported config sets `text` for plain output.
custom_instructions	No	Free-form guidance for tone, terms, audience. Max 1,000 characters.

Response shape

json

{
  "success": true,
  "request_id": "550e8400-e29b-41d4-a716-446655440000",
  "content": "Your humanized text...",
  "output_format": "text",
  "credits_used": 3
}

The output is parsed automatically (parseResponse: true), so downstream modules can map fields directly: {{2.content}}, {{2.credits_used}}, etc.

AI Checker

POST /v1/detect

Returns an AI likelihood score from 0 to 100. Higher means more AI patterns detected. Free, 30 checks per day per account, shared between the HumanTone web app and the API.

json

{
  "subflows": [
    {
      "flow": [
        {
          "id": 1,
          "module": "http:MakeRequest",
          "version": 4,
          "parameters": {
            "authenticationType": "noAuth"
          },
          "mapper": {
            "url": "https://api.humantone.io/v1/detect",
            "method": "post",
            "headers": [
              {
                "name": "Authorization",
                "value": "Bearer ht_your_api_key"
              }
            ],
            "contentType": "json",
            "inputMethod": "jsonString",
            "jsonStringBodyContent": "{\n  \"content\": \"\"\n}",
            "parseResponse": true
          },
          "metadata": {
            "designer": {
              "x": 0,
              "y": 0
            }
          }
        }
      ]
    }
  ],
  "metadata": {
    "version": 1
  }
}

Body fields

Field	Required	Notes
content	Yes	The text to analyze.

Response shape

json

{
  "success": true,
  "ai_score": 87
}

When the daily limit is reached, the API returns HTTP 200 with success: false and a time_to_next_renew field (seconds until reset). Use a Router with a filter on success to handle both cases gracefully.

Get Account

GET /v1/account

Returns your plan, credit balance, and subscription status. Useful for checking remaining credits before running a batch scenario.

json

{
  "subflows": [
    {
      "flow": [
        {
          "id": 1,
          "module": "http:MakeRequest",
          "version": 4,
          "parameters": {
            "authenticationType": "noAuth"
          },
          "mapper": {
            "url": "https://api.humantone.io/v1/account",
            "method": "get",
            "headers": [
              {
                "name": "Authorization",
                "value": "Bearer ht_your_api_key"
              }
            ],
            "parseResponse": true
          },
          "metadata": {
            "designer": {
              "x": 0,
              "y": 0
            }
          }
        }
      ]
    }
  ],
  "metadata": {
    "version": 1
  }
}

Response shape

json

{
  "plan": {
    "id": "pro_monthly",
    "name": "Pro Monthly",
    "max_words": 1500,
    "monthly_credits": 1000,
    "api_access": true
  },
  "credits": {
    "trial": 0,
    "subscription": 820,
    "extra": 150,
    "total": 970
  },
  "subscription": {
    "active": true,
    "expires_at": "2026-05-08T00:00:00.000Z"
  }
}

Workflow examples

Example 1: AI text generation, humanized before publishing.

The most common pattern. Generate text with the OpenAI, Anthropic, or any AI module, then humanize before posting it to your CMS, Notion, Slack, or sending it as an email.

flow

Trigger → OpenAI / Anthropic / any AI module → HumanTone (Humanize) → Notion / WordPress / Slack

In the HumanTone module, set content in the JSON body to the AI module's output, e.g. {{1.choices[0].message.content}}. Pick humanization_level: standard for most cases.

Example 2: AI checking on incoming form submissions.

Run a quick AI check on user-submitted text before saving it to your CRM or notifying your team. Useful for lead qualification, content moderation, or research workflows.

flow

Webhook (form submission) → HumanTone (AI Checker) → Router
                                                    ↓ if ai_score > 80
                                                    Slack notification
                                                    ↓ else
                                                    Save to CRM

Example 3: Pre-batch credit check.

Before processing a batch of articles, check that you have enough credits. Avoids mid-batch failures.

flow

Manual Trigger → HumanTone (Get Account) → Router → if credits.total < 200 → Email yourself
                                                  ↓ else
                                                  Iterator over articles → HumanTone (Humanize)

Limits

Limit	Detail
Per-request word limit	Basic 750 · Standard 1,000 · Pro 1,500
Minimum input	30 words
Credits	Humanize uses 1 credit per 100 words. Detect and Get Account do not consume credits.
AI checker quota	30 checks per day per account, shared between the HumanTone web app and the API.
API access	Included on all paid plans. Free trial accounts cannot use the API.
Plan support	Works on every Make plan that supports the HTTP module (all current plans).

For the full error reference (HTTP codes, error messages, what each one means), see the API documentation.

Note: Make's HTTP module retries on certain network errors by default. Humanize calls consume credits, so set the module's Number of retries to 0 if you want strict at-most-once delivery. AI checker and Get Account are safe to retry.

Pricing

Make scenarios share the same HumanTone credit balance you already use in the app and via direct API. No separate pricing for Make, no per-call fees, no platform surcharge.

What you need	Where to get it
A paid plan (Basic, Standard, or Pro)	humantone.io/pricing
An API key	app.humantone.io/settings/api
More credits	Buy Extra Credits in your dashboard. No plan change required.

FAQ

How do I humanize AI text in Make.com?

Which Make module calls the HumanTone API?

Can I use HumanTone with Make.com's free plan?

How do I handle errors in the HTTP module?

Does Make.com count HumanTone credits separately?

How do I avoid duplicate humanize calls if my scenario retries?

Other platforms

If you use HumanTone elsewhere:

Platform	Path
n8n	HumanTone for n8n
Claude Desktop, Cursor, VSCode, any MCP client	MCP server
Direct API (any language)	API documentation

HumanTone for Make.

Overview

Setup

POST /v1/humanize

Body fields to configure

Response shape

POST /v1/detect

Body fields

Response shape

GET /v1/account

Response shape

Workflow examples

Example 1: AI text generation, humanized before publishing.

Example 2: AI checking on incoming form submissions.

Example 3: Pre-batch credit check.

Limits

Pricing

FAQ

Other platforms