Resources · Make integration

Langdock Make integrationAutomate Langdock with Make.

What if every new row, email or form entry got an AI answer without anyone opening a chat window? The Langdock Make integration gives you 4 action modules that send a prompt to a model and hand the reply to the rest of your workflow. This page walks you through the connection, a first scenario and each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Langdock Make integration do for you?

The Langdock Make integration lets a Make scenario, the automation you build in Make, ask a model a question through your Langdock account and reuse the answer. Langdock has no trigger in Make, so something else starts the flow: another app, or a schedule set in Make. Langdock then does the thinking step in the middle.

Summaries that write themselves. A support ticket lands in your helpdesk app, Create an OpenAI Chat Completion turns it into a three-line brief, and the next module posts that brief where your team reads it.

A second opinion on the same text. Pass a draft to Send an Anthropic Message after the OpenAI module and ask it to check tone or spot missing facts. Two models, one scenario, one Langdock key.

Code help on demand. When a developer drops a snippet in a shared table, Create a Codestral can return a response you store next to it. If a Langdock endpoint is not covered, Make an API Call reaches it with the same connection.

What Make does not do here: watch Langdock for events. There is no trigger, so the scenario always starts from another app or from its schedule. Records coming from a base like the one in the Airtable Make integration are a common starting point.

Langdock may also exist as a node in n8n. Before choosing, read n8n vs Make, and if you want a structured path into Make itself, the Make training covers the editor step by step.

Connect

How do you connect Langdock to Make?

  1. 01

    Get an API key in Langdock

    Log in to Langdock, open the settings section and find the area for API keys. If you cannot create one yourself, ask your Langdock admin for a key. Copy it once it appears, you will paste it in Make a moment later.

  2. 02

    Add a Langdock module in Make

    In your scenario, add any Langdock module and click Create a connection. A connection is your Langdock account linked to Make once, then reused by all four modules. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Langdock into the credentials field and follow the on-screen instructions to finish. Make then keeps the connection, so the next Langdock module you add simply offers it in a list.

First scenario

Your first scenario with Langdock

GoalWhen a new record shows up in another app, Make asks Langdock for a draft, then asks a second model to review it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your source data, for example a table of incoming requests, and connect it.

  2. 02

    Add the OpenAI chat module

    Click the + on the right of that first module, search Langdock and choose Create an OpenAI Chat Completion. Create the connection with your API key, then map the text of the request into the message you send.

  3. 03

    Add the Anthropic review

    Add Send an Anthropic Message after it. Map the reply from the previous module into your message and ask the model to check the draft. Each item that flows through is a bundle: here, one request and its answer.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can read both answers and adjust your prompts before anything goes live.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Modules

What the Langdock modules do

Langdock gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Langdock1

Create a Codestral

Action

In MakeCreates a model response for the given chat conversation using an OpenAI model.

You get a model reply to a chat conversation through your Langdock account, ready to store or pass on. Its name points to code, so try it first when your prompt is about a script.

When to use it
a developer adds a snippet to a shared table and you want an explanation saved in the next column.
Watch out
Make's directory describes it with the same words as the OpenAI module, so run it once and read the output before relying on it.
Langdock2

Create an OpenAI Chat Completion

Action

In MakeCreates a model response for the given chat conversation using an OpenAI model.

This one hands you an answer from an OpenAI model for the conversation you build from earlier modules. Put the text you want processed in the message, and the reply comes back as data you can map anywhere after it.

When to use it
a new support ticket arrives and you want a short summary or a suggested reply before a person looks at it.
Watch out
each run counts as one operation, meaning one execution of one module, so a scenario handling many bundles uses many.
Langdock3

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

With this module you can reach any endpoint of the Langdock API, reusing the connection you already created, so there is no second key to manage. It fills the gap when the three ready-made modules do not cover what you need.

When to use it
you found a Langdock feature in its API documentation that has no dedicated module in Make.
Watch out
you write the request yourself, so check the endpoint in Langdock's own documentation first.
Langdock4

Send an Anthropic Message

Action

In MakeCreates a model response given a structured list of input messages using the Anthropic API.

Here the reply comes from the Anthropic API: you pass the conversation as an ordered set of messages and get the model's answer back, ready to map. It is the natural choice when your team prefers Anthropic models for a given task.

When to use it
a draft produced earlier in the scenario needs a review for tone or missing facts before it is sent.
Watch out
the list of messages follows an order, so map the earlier replies in the order you want the model to read them.
Need help

Need help automating Langdock with Make?

A person reads every message.

FAQ

Langdock and Make: common questions

01Is the Langdock Make integration free?
Yes, on the Make side. Langdock is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, caps each run at 5 minutes and includes 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. Your Langdock account and its API key are separate, and this page does not cover what Langdock charges.
02What do you need to connect Langdock to Make?
An active Langdock account and an API key. You find API keys in the settings section of Langdock. If your workspace does not let you create one, your admin has to generate it for you. In Make, add a Langdock module, click Create a connection, optionally name the connection, then paste the key. From then on, all four Langdock modules reuse that same connection, so you only do this once per account.
03Can a Langdock scenario start in real time?
Not from Langdock itself, because the app has no trigger module in Make. The scenario starts another way. The first option is a trigger from another app, such as a new record in a table or a new ticket, placed before the Langdock module. The second is the schedule on the first module: a new scenario runs every 15 minutes by default. Whether that start is instant depends entirely on the trigger of the other app you choose.
04What if a Langdock feature is missing from the Make modules?
Use Make an API Call. The Langdock app includes it, and it lets the scenario call any endpoint of the Langdock API with the connection you already have. That covers what the three ready-made modules do not. Keep in mind that Make's documentation for this app is marked as AI-generated from Langdock's own docs and may contain errors, so confirm the important details with Langdock directly before you build on them.
05Should you use Make or n8n for Langdock?
It depends on the tool you already run. Langdock may also be available as an n8n node, and both tools can place an AI step inside a larger workflow. In Make, you get 4 Langdock modules today: two chat modules, one Anthropic module and Make an API Call for the rest. The practical test is simple: build the scenario you need with the modules listed here, and if the steps around Langdock already live in one of the two tools, stay there.