Update Trigger

Update an existing trigger in an integration

Updates an existing trigger in an integration. This replaces the trigger configuration with the provided values.

Base URL

https://api.langdock.com/integrations/v1/{integrationId}/triggers/{triggerId}

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
triggerId	string	Yes	UUID of the trigger to update

Request Body

Parameter	Type	Required	Description
name	string	Yes	Trigger name (max 100 characters)
description	string	No	Trigger description (max 90 characters)
pollingCode	string	No	JavaScript code to poll for new events (max 1,000 characters)
inputFields	array	No	Input fields for configuring the trigger

See Create Trigger for the full input field schema.

Sending the same field label keeps the field’s stored data.input key when that key is the camelCase form of the label. This includes the older casing from earlier Integrations API versions, such as officeID for Office ID, so existing polling code keeps working.

Example

const axios = require("axios");

async function updateTrigger(integrationId, triggerId) {
  const response = await axios.put(
    `https://api.langdock.com/integrations/v1/${integrationId}/triggers/${triggerId}`,
    {
      name: "New Issue Created v2",
      description: "Updated trigger with additional filtering options",
      pollingCode: `
        const response = await ld.request({
          method: "GET",
          url: "https://api.example.com/v2/issues",
          headers: {
            Authorization: "Bearer " + data.auth.apiToken
          },
          params: {
            since: new Date(Date.now() - 60 * 60 * 1000).toISOString(),
            project: data.input.projectId
          }
        });
        return response.json;
      `,
      inputFields: [
        {
          label: "Project ID",
          type: "TEXT",
          required: true
        },
        {
          label: "Status Filter",
          type: "SELECT",
          options: [
            { label: "All", value: "all" },
            { label: "Open", value: "open" },
            { label: "Closed", value: "closed" }
          ],
          required: false
        }
      ]
    },
    {
      headers: {
        Authorization: "Bearer YOUR_API_KEY",
        "Content-Type": "application/json"
      }
    }
  );

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

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

Response Format

Success Response (200 OK)

{
  trigger: {
    id: string;
    name: string;
    slug: string;
    description: string;
    type: string;
    pollingCode: string | null;
    inputFields: Array<{
      slug: string;
      label: string;
      type: string;
      description: string;
      placeholder: string | null;
      required: boolean;
      options: Array<{label: string, value: string}> | null;
      allowMultiSelect: boolean | 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 trigger not found
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.