Update Action

Update an existing action in an integration

Updates an existing action in an integration. Changing name does not change the action slug.

Base URL

https://api.langdock.com/integrations/v1/{integrationId}/actions/{actionId}

Dedicated deployments

Replace api.langdock.com with <your-deployment-url>/api/public in all requests.

Required Scopes

This endpoint requires the INTEGRATION_API scope.

Parameters

Path Parameters

Parameter	Type	Required	Description
integrationId	string	Yes	UUID of the integration
actionId	string	Yes	UUID of the action to update

Request Body

Parameter	Type	Required	Description
name	string	Yes	Action name (max 100 characters)
description	string	No	Action description (max 1,000 characters)
code	string	No	JavaScript code to execute (max 150,000 characters)
inputFields	array	No	Input fields for the action
requiresConfirmation	boolean	No	Whether the action requires user confirmation before running

See Create Action for the full input field schema.

If you omit description, it is cleared. If you omit inputFields, all existing input fields are removed. If you omit code or requiresConfirmation, the current value is preserved. Supplying inputFields replaces the complete field list. If an input field omits jsonSchema, the existing JSON Schema is preserved when the slug generated from the submitted field label matches. To remove a JSON Schema, send jsonSchema: null explicitly.

Example

const axios = require("axios");

async function updateAction(integrationId, actionId) {
  const response = await axios.put(
    `https://api.langdock.com/integrations/v1/${integrationId}/actions/${actionId}`,
    {
      name: "Get User Data v2",
      description: "Updated action with additional fields",
      code: `
        const response = await ld.request({
          method: "GET",
          url: "https://api.example.com/v2/users/" + data.input.userId
        });
        return response.json;
      `,
      inputFields: [
        {
          label: "User ID",
          type: "TEXT",
          required: true
        },
        {
          label: "Format",
          type: "SELECT",
          options: [
            { label: "JSON", value: "json" },
            { label: "XML", value: "xml" }
          ],
          required: false
        }
      ]
    },
    {
      headers: {
        Authorization: "Bearer YOUR_API_KEY",
        "Content-Type": "application/json"
      }
    }
  );

  console.log("Updated action:", response.data.action);
}

updateAction("550e8400-e29b-41d4-a716-446655440000", "660e8400-e29b-41d4-a716-446655440001");

Response Format

Success Response (200 OK)

{
  action: {
    id: string;
    name: string;
    slug: string;
    description: string;
    code: string | null;
    order: number;
    requiresConfirmation: boolean;
    inputFields: Array<{
      slug: string;
      label: string;
      type: string;
      description: string;
      placeholder: string | null;
      required: boolean;
      order: number;
      options: Array<{label: string, value: string}> | null;
      allowMultiSelect: boolean | null;
      contextActionId: string | null;
      jsonSchema: string | null;
    }>;
  };
}

Error Handling

Status Code	Description
400	Invalid request body or IDs
401	Invalid or missing API key
403	No access to this integration
404	Integration or action not found
422	Unsupported integration type. Update actions only on a workspace owned API integration.
429	Rate limit exceeded

Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.