Resources · Make integration

llama-api.com Make integrationAutomate llama-api.com with Make.

Can Make send your text to llama-api.com and hand the reply to your other tools? The llama-api.com Make integration gives you 2 action modules and no trigger. This guide is for people new to Make: it shows how to link your account, build a first scenario and test it safely.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the llama-api.com Make integration do for you?

The llama-api.com Make integration lets a Make scenario, the automation you build as a chain of bricks, call llama-api.com without code. Each brick is a module; here you get two actions: Create Chat Completions, and Make an API Call for anything the first one does not cover.

Draft answers for a support inbox. A message arrives in your helpdesk app, the scenario passes its text to Create Chat Completions, and the generated reply goes back to the ticket as a draft for an agent to check. The name of the module points to this chat style of request.

Summarize form entries for sales. A lead fills in a form in another app, Create Chat Completions turns the free text into a short brief, and the brief lands in your CRM. Pages like the 123FormBuilder Make integration cover the form side.

Reach the rest of the API. When you need an endpoint the listed module does not expose, Make an API Call uses the same connection and lets you call it yourself.

Know the limits before you start. Make's own documentation for llama-api.com is marked as limited: there is not enough public information for a complete guide, so field names and quotas are not documented there. Test every step with Run once. If you also work with n8n, the n8n vs Make comparison sets the two tools side by side, and the Make training helps you get comfortable with the editor.

Connect

How do you connect your llama-api.com account to Make?

  1. 01

    Add a llama-api.com module

    Open your scenario, search for llama-api.com and pick one of its two modules. In the module panel, click Create a connection. A connection is your llama-api.com account linked to Make once, then reused by every module of the app.

  2. 02

    Name the connection

    This step is optional, but a clear name helps later. If you keep a test account and a production account, label them so you never send live requests from the wrong one when you copy a scenario.

  3. 03

    Authorize Make and save

    Depending on what the app asks for, either authorize Make on the llama-api.com page that opens, or paste the key that llama-api.com gives you. Then click Save, and the connection appears in the module.

First scenario

Your first scenario with llama-api.com

GoalWhen a new message reaches another app, Make sends its text to llama-api.com and passes the generated reply to the next module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your messages, such as your helpdesk or form tool.

  2. 02

    Add Create Chat Completions

    Click the + on the right of that first module, search llama-api.com and choose Create Chat Completions. Select the connection you made earlier.

  3. 03

    Map the incoming text

    Fill the module fields and map the message text coming from the first module. Each item passed along is a bundle: one message, one form entry, one row.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received, including the reply from llama-api.com.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From then on, Make counts each module run on each bundle as one operation on your plan.

Modules

What the llama-api.com modules do

llama-api.com gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

llama-api.com1

Create Chat Completions

ActionIn the docs only

This is the module you reach for when a scenario should get generated text back from llama-api.com, based on text you pass in from an earlier step. Its name refers to a chat completion request; the reply comes out as a bundle.

When to use it
a customer message or a form answer needs a draft reply or a summary before it moves on.
Watch out
Make's documentation does not describe the fields of this module, so read the output in Run once before mapping it.
llama-api.com2

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the llama-api.com API from your scenario, reusing the connection you already created. It is the way out when Create Chat Completions does not offer the request you need.

When to use it
you know the endpoint you want from the llama-api.com side and no listed module covers it.
Watch out
you write the request yourself, so check whatever documentation llama-api.com gives you for the path and the body it expects.
Need help

Need help automating llama-api.com with Make?

A person reads every message.

FAQ

Questions about llama-api.com and Make

01Is the llama-api.com Make integration free?
Yes, on the Make side. llama-api.com is a standard app, so it is available from the Free plan. That plan lets you keep 2 active scenarios, with at least 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow 40 minutes of execution. Each module run on a bundle counts as one operation. Your own llama-api.com account is a separate matter, and this page gives no price for it.
02What do you need to connect llama-api.com to Make?
You need a llama-api.com account and a Make account. Make's documentation lists no prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add a llama-api.com module, click Create a connection, optionally name it, then authorize Make on the app page or paste the key the app provides, and click Save. The connection is then reused by both modules. If something fails, look at your llama-api.com account to see which access method it offers.
03Does llama-api.com trigger a Make scenario in real time?
No, because llama-api.com has no trigger module in Make. Both modules are actions, so something else has to start the scenario. You can open it with a trigger from another app, for instance a new ticket or a new form entry, and the scenario starts from each new item that app hands over. You can also start with a schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan does not go below that interval. Either way, llama-api.com comes in as the second step.
04What if a llama-api.com module is missing in Make?
Use Make an API Call. That module lets the scenario call any endpoint of the llama-api.com API with the same connection, so you are not limited to Create Chat Completions. Keep in mind that Make's documentation for this app is marked as limited, since there is not enough public information for a full guide. That means you rely on what llama-api.com documents on its side for the request itself, and on Run once to check what comes back before you switch the scenario on.
05Should you use Make or n8n with llama-api.com?
It depends on the tool your team already uses. This page covers Make, where llama-api.com offers two action modules: Create Chat Completions and Make an API Call. Many apps also have an n8n node, but this page cannot confirm one for llama-api.com, so check the n8n side before you decide. Compare the criteria that matter to you, such as how you prefer to build, who maintains the scenarios and which other apps sit in the flow. The n8n vs Make comparison linked above goes through those points.