Your code. Connected to your business.
Make Endpoints calls app actions from JavaScript, TypeScript or REST through the connections your team already manages in Make. Keep the logic in your code; Make handles the connection.
500,000+ companies have saved millions of hours with Make
Make Endpoints
Keep the logic in your code. Connect the apps.
Choose an endpoint, pass its inputs and a Make connection, and work with the output in your own program. No app credentials in the call, and no scenario built just to wrap a single action.
How does Make Endpoints work?
From code to a connected app in 3 steps.
Discover an action
Choose your Make team, find an endpoint your team can use and inspect its inputs. The CLI lists every endpoint in the package and describes one in detail.
Call it from code
Authenticate to Make with your API key, pick the connection and send the endpoint's inputs from JavaScript or TypeScript. No provider credentials in the call.
Build on the result
Generated methods return the endpoint's output directly. Check it, handle pagination and errors, and add your own logic around the call.
Benefits
Why use Make Endpoints
Make Endpoints brings the connections your team manages in Make into the code you already write.
%201.svg)
+2
Date
·
Duration
Build where you work
Use REST, JavaScript or TypeScript. Keep your libraries, tests and control flow in your own codebase.
.avif)
+2
Date
·
Duration
Use connections managed by Make
Reference a Make connection by its ID instead of passing provider credentials. Make API authentication and team permissions still apply.
+2
Date
·
Duration
Discover before you build
Start from the endpoints your team can use. App metadata and generated types describe every input and output.
Advanced use case
From Gmail to a briefing you can review.
Read selected messages through an endpoint, prepare Slack-ready text in your code, and stop there. Nothing posts until someone approves it.
One bounded query, a capped page size, and no changes to the mailbox.
Use cases
What builders do with Endpoints
Start with one useful read, then build from there.
Date
·
Duration
Mailbox briefing
List and read selected messages in Gmail, then prepare Slack-ready text for review. Nothing posts until someone approves it.
Date
·
Duration
Context for an internal tool
Pull a Google Docs document or recent Gmail messages into an internal tool, where a whole scenario would be overkill.
Date
·
Duration
Bounded AI helper
Give your agent only the endpoints the task needs with EndpointTools. Validate inputs and keep writes behind explicit approval.
Date
·
Duration
Reuse a Make connection
Already connected an app in Make? Use the same connection from a script, check coverage with make-endpoints-cli, and keep the scenarios that already work.
Applications
Your Make connections, now in your code
Endpoints run through the connections your team already manages in Make, with typed inputs and outputs for every action. Check which endpoints your team can use before you build.
Learn
What are Make Endpoints?
Understand when to call an app action from code, and how to start.
Date
·
Duration
6 min read · October 21, 2026
Make Endpoints vs Composio: which one fits your code?
Description
Both let code call app actions without building every integration. They're built for different jobs. Here's how to pick.
Date
·
Duration
Developer docs · Closed beta
Make Endpoints SDK: call an app action from JavaScript
Description
Install @makehq/endpoints-sdk, create a Make client and call your first endpoint with an existing connection.
Date
·
Duration
Developer docs · CLI
make-endpoints-cli: discover endpoints for your agent
Description
List the endpoints in the package, describe one, and give your agent only the tools the task needs.
Support
FAQs
Everything you need to know about Make Endpoints. Can't find the answer you're looking for? Please chat to our team.
What is Make Endpoints?
Make Endpoints lets you call a single app action from your own code, without building a scenario. You choose an endpoint, pass its inputs and a Make connection, and get the output back.
Your code runs where you run it. Make executes the app action through the connection your team already manages.
How much does Make Endpoints cost?
During the Beta, each endpoint call costs 0.1 credit, so 10,000 credits cover 100,000 calls. Credits come from your Make plan.
Do I need a Make API key?
Yes. A Make API key with the endpoints:run scope authenticates your request, and team permissions still apply. The connection ID selects the app account; never put an app's credentials in the endpoint's input.
Can I call any app action?
Use team-scoped discovery or make-endpoints-cli to see what's available. Not every Make app has endpoints yet, so check coverage before you build.
What is the difference between Make Endpoints and Make MCP Server?
Make MCP Server exposes your Make scenarios as tools that AI clients like Claude or ChatGPT can call. Make Endpoints is for your own code: it calls individual app actions directly from JavaScript, TypeScript or REST.
In short: MCP Server = your scenarios as AI tools. Endpoints = app actions in your code.
Do I need to rebuild my scenarios?
No. Endpoints is another way to run app actions, not a migration. Keep visual workflows in scenarios and use Endpoints where the logic belongs in code.