Source: https://ailoot.ai/docs/en/integrations/make/
Canonical: https://ailoot.ai/docs/en/integrations/make/
Language: en

[Automation](https://ailoot.ai/docs/en/integrations/#automation) 

# Make

[Markdown](https://ailoot.ai/docs/en/integrations/make/index.md)

No-code automation · HTTP request

| Format | Where to set it up |
| --- | --- |
| HTTP request | The built-in OpenAI module works only with an OpenAI account. Use HTTP → Make a request: URL, Method, Headers, Body type Raw / JSON |

## [](https://ailoot.ai/docs/en/integrations/make/#setup)Setup

Copy the configuration and replace `sk-...` with your key from the Ailoot Dashboard. Prefer storing the key in the environment variable `AILOOT_API_KEY`, if the application supports it.

Before starting, request GET /v1/models with your Ailoot key. Choose an exact model ID whose methods include POST /v1/chat/completions, then use that ID in the configuration. For agents, also check tool support and the features required by your client version.

```text
Module: HTTP → Make a request
URL: https://api.ailoot.ai/v1/chat/completions
Method: POST
Headers:
  Authorization: Bearer sk-...
  Content-Type: application/json
Body (JSON):
{"model":"gpt-6.1-sol","messages":[{"role":"user","content":"{{1.text}}"}]}
Parse response: Yes → the response is in choices[].message.content
```

Example model: `gpt-6.1-sol, claude-sonnet-5-5`. Choose any other model from the [catalog](https://ailoot.ai/models/en/) — check that it supports the format you need.

## [](https://ailoot.ai/docs/en/integrations/make/#notes)Good to know

This is a general-purpose HTTP module, not a dedicated Ailoot provider: its documentation allows any HTTPS URL. Store the key in an API-key connection, as Make recommends, rather than passing it in headers. Make does not need streaming output; omit stream.

## [](https://ailoot.ai/docs/en/integrations/make/#check)Test

- Ask a short question. If you get an error, check the code and Request ID, then consult [Errors and limits](https://ailoot.ai/docs/en/errors/).
- 404 immediately after setup almost always means the URL is wrong: an extra or missing `/v1`.
- 402 — insufficient balance for the reserve. Agents reserve more than chat: [why](https://ailoot.ai/docs/en/billing/reserve/).

Application documentation: [https://apps.make.com/http](https://apps.make.com/http)

Still have questions? Send your Request ID and a description — we'll help you troubleshoot.[Contact support](mailto:support@ailoot.ai)

## Ailoot · The company and its project portfolio





Ailoot combines established operating experience, a large client base, stable service and ongoing KPI control.





The company and its project portfolio: millions of customers; monthly sales in the billions.





Ailoot brings that operating experience to API access for AI features in customer products, agents, applications and automations.