Skip to content
Hypamoon

Developer tools

Connect Make to Hypamoon

Yes. Make has a public, versioned API and you create the key yourself, so your chat can write the adapter.

Open

The check

Three questions about the API of Make, answered from its own docs.

Public API docs
Yes. Read the docs
A key you create yourself
Yes. You create an API token yourself in your Make profile and choose its scopes. developers.make.com
Versions or a changelog
Yes. The version is in the path, such as /api/v2. developers.make.com
How it signs in
An API token in the Authorization header, as Token followed by the token. OAuth 2.0 clients are available on request.
Webhooks
Yes. It can tell your app when something changes. developers.make.com
Hosting
Cloud
Condition
Most API endpoints are on paid plans. Use the base URL of your own zone, such as eu1.make.com.

Your own control room for Make, in plain questions.

  • Scenarios and their logs, from the Make API v2.
  • AI that reads a failed scenario run and explains what went wrong.
  • A weekly email with the scenarios that need attention.

Ask your chat

Answers straight from your Make data, in Claude or another chat with the full Hypamoon connection.

  • Which scenarios had errors this week?
  • Which scenario used the most operations this month?

On a schedule

An agent checks Make every 15 minutes and decides what happens next.

  1. Every 15 minutes

    Every Monday morning.

    AI decides

    AI reads the scenario logs of the past week and sorts the errors.

    Then

    A short summary is emailed to you.

Add Hypamoon

Text messages, email, phone, payments and agents run in the same project as the adapter.

  • Agent on a schedule

    An agent that answers questions about your scenarios, with a read-only token.

Make stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in Make waits for your approval, one call at a time. How adapters work

Good to know

  • Your adapter uses a fixed key: you paste it once in the Hypamoon portal, never in the chat, and it only goes to the API host you allow.
  • Create a separate token per zone, and give it only the scopes it needs, such as scenarios:read.

Try it in your chat

Fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for Make. API docs: https://developers.make.com/api-documentation. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 11 November 2026.

Make is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Make. Found something that changed? Tell us at support.

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect Make?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot