> For the complete documentation index, see [llms.txt](https://docs.aimlapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aimlapi.com/integrations/make.md).
# Make
## About
Make is a powerful, enterprise-scale automation platform. It offers flow control, data manipulation, HTTP/webhooks, AI agents and tools, notes, an MCP server, and many other features at your service.
## How to Use AIML API via Make
You work with Make through the browser; there’s no need to install any components separately.
1. First, you need a [Make account](https://www.make.com/en/register).
2. Next, click on **Scenarios** in the left menu.\
\
3. Choose **AI/ML API** option:
4. Choose **Get a Model Response**:
5. Click on **Create a Connection**, provide a name, and paste your [AIMLAPI key](https://aimlapi.com/app/keys):
6. Once that’s done, you’ll be able to configure the model and enter your prompt in the provided field:
7. Then just click **Run once**:
\
When the model returns a response, you’ll see it to the right of your node:
\
You can find more details in the [official documentation](https://help.make.com/create-your-first-scenario).
## Our Supported Models
Any of our [text models](/api-references/text-models-llm.md#complete-text-model-list) can be used to process your requests — for instance, [gpt-4o](/api-references/text-models-llm/openai/gpt-4o.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aimlapi.com/integrations/make.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
