When using Langdock module in make.com I get the 410 error for Agent API

Questions
, ,
1

:bullseye: What is your goal?

I what to continue using the Langdock module in my make workflow. It used to work perfectly until recently.

:thinking: What is the problem & what have you tried?

Dear Community,
Does anyone know how to solve this issue?
I use Langdock in my make.com workflow and it used to work perfectly before the API change. Apparently the connector is not yet updated. Langdock Support pointed to make.com support for further assitance with the connector.
Does anyone know when this will be updated?

:clipboard: Error messages or input/output bundles

[410] As of August 20, 2026, the Assistant API has been deprecated. Please use the Agent API instead.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Error Message_API.jpg
Error Message_API.jpg432×390 42.9 KB

3

Hey there,

You can use a generic http call while waiting for the module to get updated.

5

The 410 is Langdock retiring Assistant, not Make breaking your mapping. HTTP to the Agent endpoint unblocks production today; waiting on the connector just leaves the scenario down.

If you already have an Agent id in Langdock, the swap is the URL and whatever they renamed in the body. Is the Make module still sending an Assistant id, or do you already have an Agent id in their dashboard?