---
title: "Langdock: Integration für KI-Agenten"
description: "Verbinde Langdock mit Langdock. Agenten und Workflows nutzen 54 Actions, zum Beispiel „Change knowledge access“ und „Chat with agent“."
url: "https://langdock.com/de/integrations/langdock"
language: "de"
---

[Integrationen](https://langdock.com/de/products/integrations)

# Langdock: Integration für KI-Agenten

Build agents, manage integrations, and search your knowledge base

Verbinde Langdock mit Langdock und nutze es im Chat, in Agenten und in Workflows.

54 Actions · 2 Triggers

[Kostenlos testen](https://app.langdock.com/signup) [Mit Sales sprechen](https://langdock.com/de/talk-to-sales)

Beschreibungen, Actions und Beispiel-Prompts kommen direkt aus dem Produkt und sind dort auf Englisch verfasst.

## Actions für Langdock

Jede Action ist ein Schritt, den ein Agent oder Workflow in Langdock ausführen kann.

- Change knowledge access

  Changes the role (Viewer or Editor) that one person or workspace API key has on a Langdock knowledge base, for example to promote a viewer to editor. Takes a user ID or API key ID; to find a person's user ID from their email, use Find user first. Creates the grant if they had no direct access. The knowledge base owner's access cannot be changed. The connection's key needs the KNOWLEDGE_FOLDER_API scope and Editor access on the knowledge base.
- Chat with agent

  Sends a conversation to an agent and returns the non-streaming completion response
- Create action

  Creates a new action for a custom workspace integration (public: false), including whether it requires confirmation. Actions are executable functions that can be invoked by agents and workflows. Does not apply to built-in catalog integrations.
- Create agent

  Creates a new agent in the workspace with optional instructions, model, capabilities, skills, and integration actions. Requires ASSISTANT_API scope.
- Create integration · Creates a new custom integration in the workspace
- Create skill · Creates a new skill in the workspace
- Create trigger

  Creates a new polling trigger for a custom workspace integration (public: false). Triggers poll for events and activate workflows. Does not apply to built-in catalog integrations.
- Create workflow

  Creates an inactive unpublished draft with an optional starter trigger. The draft belongs to the API key's owner. With a personal key that is the person running the action; with a workspace key it is the key's account, and nobody else can open the draft unless it is shared, so put the user IDs of the people who need it, or the IDs of groups they belong to, in shareWith. The workflow API has no separate share call, so sharing happens only at creation, and the response says when the requester cannot open the draft. Add the trigger and steps afterwards with Update workflow for the returned workflow ID. Does not publish the workflow or start schedules and webhooks. The response includes a url that opens the workflow in the builder. Templates cannot be created. Requires WORKFLOW_WRITE_API scope and the createWorkflows permission; shareWith also needs shareWorkflows. Always pass the returned review notices on to the user: the workflow has to be checked in the builder, where connections are chosen.
- Delete action

  Permanently deletes an action from a custom workspace integration (public: false). Does not apply to built-in catalog integrations
- Delete attachment · Deletes an uploaded attachment by ID
- Delete knowledge file · Deletes a file from a knowledge folder
- Delete skill · Permanently deletes a skill from the workspace
- Delete trigger

  Permanently deletes a trigger from a custom workspace integration (public: false). Does not apply to built-in catalog integrations
- Delete workflow

  Permanently deletes a workflow, including its draft and published versions. Requires WORKFLOW_DELETE_API scope and editor access. This scope cannot be granted on a personal API key. The in-app builder still requires owner access.
- Disable or enable agent · Disables or re-enables an agent for API and workspace use
- Export usage (deprecated)

  Deprecated: use the Langdock Admin integration instead. Exports workspace usage data for the given date range. Pick the dataset (agents, assistants, users, workflows, projects, or models) and a from/to range; returns the matching records inline, or a CSV download when output format is file. Requires USAGE_EXPORT_API scope.
- Export workflow runs

  Exports workflow run and node execution data for a date range as flattened rows, one per node execution. Returns rows inline by default; results over 50 rows are returned as an attached CSV (same pattern as Power BI query results). Enable Return as CSV to force a file for smaller exports. Requires an API key with the WORKFLOW_API scope and workflow owner, editor, or workspace admin access.
- Get action

  Retrieves a single action from a built-in catalog integration, MCP integration, or custom workspace integration, including its version and inputFields (plus source code, order, and confirmation flag for custom integrations). Prefer this over get integration with includeDetails when you only need one action — large integrations can exceed context limits when every action's schema or code is returned together.
- Get agent

  Retrieves an agent's prompt, model, capabilities, conversation starters, attachments, attached skill IDs, and actions. Set includeDetails for API-native field names, canvas, and knowledge folder IDs. Requires ASSISTANT_API scope.
- Get integration

  Retrieves a built-in catalog integration, MCP integration, or custom workspace integration by ID. Returns a summary (name, auth type, integration type, public flag, and action/trigger list with action versions) by default. Set includeDetails for action and trigger inputFields plus custom builder fields (source code, polling code, and auth configuration) when available. Note: builder write actions only work on custom workspace integrations where public is false.
- Get knowledge file

  Retrieves details of a specific file in a knowledge folder including its processing status and summary. Requires KNOWLEDGE_FOLDER_API scope.
- Get meeting

  Loads a meeting's title, owner, attendees, times, shared notes, and transcript. Pass meetingId from File added to folder, or paste the meeting UUID from the meeting page URL. Attendees come from the linked calendar event and do not include the owner; recordings without a calendar event return an empty attendee list. Requires a personal or workspace API key with Meetings Read API scope. The key can read meetings the key owner recorded or can access through sharing. personalNotes holds the creator's manual notes, even if notesStatus is still PENDING; it needs a personal API key owned by the meeting creator and is null for workspace keys and for meetings shared by others. isCreator is true when the API key owner created the meeting, false otherwise, and null when it could not be determined; use it to let only the creator's run continue when each user runs the workflow with their own key.
- Get skill

  Retrieves a skill by ID including its instructions, attached integrations, and attached file paths. Use Get skill file to read a file's contents
- Get skill file

  Retrieves the text contents of a file attached to a skill. Use Get skill to list the skill's file paths
- Get workflow

  Reads one workflow the API key can view, including the draft graph, the published graph, version history, and execution limits. Secret-like fields are redacted. Sending that redacted graph back through Update workflow keeps the stored secrets. Requires WORKFLOW_API scope and viewer access.
- Grant knowledge access

  Shares a Langdock knowledge base as Viewer or Editor with people, by user ID, or with workspace API keys, by API key ID. To share with someone known only by email, get their user ID with Find user first. Anyone who already has access keeps their current role and is listed as unchanged; use Change knowledge access to change a role. If any ID is not an active member or a workspace API key, nothing is granted. Groups and personal API keys are not supported. The connection's key needs the KNOWLEDGE_FOLDER_API scope and Editor access on the knowledge base.
- Import skill · Imports a skill from a markdown or zip file
- Invite users (deprecated)

  Deprecated: use the Langdock Admin integration instead. Invites one or more users to the workspace by email. Already-existing members are silently skipped. Pending join requests are automatically approved. Requires USER_MANAGEMENT_API scope and admin API key.
- List agents

  Lists agents shared with the API key in the connected Langdock workspace. Returns summaries by default or full agent details when requested. Requires ASSISTANT_API scope
- List connections

  Lists integration connections owned by or shared with the API key user. Can be filtered by actionId (server-side) or integrationId and onlyValid (client-side). Returned connection IDs can be pinned on agent actions in create agent and update agent. Note: OAuth connections are only returned when the API key user has the configurePreselectedConnections workspace permission. Requires ASSISTANT_API or AGENT_WRITE_API scope.
- List integrations

  Lists integrations available in the workspace (both built-in catalog integrations and custom workspace integrations). Returns id and name by default. Set onlyCustom to list only custom workspace-owned integrations that can be edited with builder write actions, or set includeDetails for description, auth type, integration type, and custom action summaries.
- List knowledge bases

  Lists the Langdock knowledge bases this connection can open, with each one's ID, name, description, file count, and role (Viewer or Editor). A workspace API key lists knowledge bases shared with that key. A personal API key lists the knowledge bases its owner can open, with the owner's role. Use it to find a knowledge base ID before searching, listing files, renaming, or sharing it. Knowledge bases the key cannot open do not appear. This lists knowledge bases, not the files inside one; use List knowledge files for that. Needs the KNOWLEDGE_FOLDER_API scope.
- List knowledge files

  Lists all files in a knowledge folder including their processing status. Requires KNOWLEDGE_FOLDER_API scope.
- List meetings

  Lists Langdock meetings the key owner recorded, newest end time first; meetings still in progress come first. Optionally includes meetings shared with them. Filter by search term, attendee email, company domain, notes status, or end-time range. Returns meeting IDs and metadata without notes or transcripts; pass an ID to Get meeting to read them. Scheduled and deleted meetings are never listed. Requires a personal or workspace API key with Meetings Read API scope.
- List models

  Lists all available models for use with the Agent API, including their regions and capabilities. Requires ASSISTANT_API scope.
- List skills

  Lists skills in the workspace with optional search. Returns a short summary by default. Set includeDetails to include instructions and attached integration IDs. Pages the API automatically up to the limit
- List workflow runs

  Lists paginated workflow runs with node inputs, outputs, errors, and logs for a workflow the API key can edit. Filters include test versus production, status, version, and a creation-time range. This is not Export workflow runs, which is a separate date-bounded flattened row dump capped at 10000 runs. Requires WORKFLOW_API scope and editor access.
- List workflows

  Lists non-template workflows visible to the API key. Workspace admin identities see every non-template workflow. Returns summaries without the graph; use Get workflow for the draft and published graphs. Pages automatically up to the limit. Requires WORKFLOW_API scope and viewer access.
- Publish agent · Publishes draft changes on an agent as a new version
- Publish workflow

  Publishes the current draft as a new production version, marks the workflow active, and starts scheduled and webhook triggers. Rejected when the draft trigger is disconnected, when an unauthenticated webhook violates the workspace rule, when the workflow is a template, or when there is no draft. Also refused while the draft has placeholder (add) steps, which must be replaced in the builder first. Pause a live workflow with Update workflow and status INACTIVE. Requires WORKFLOW_WRITE_API and WORKFLOW_API scopes and editor access. Always pass the returned review notices on to the user: the workflow has to be checked in the builder, where connections are chosen.
- Read folder file

  Reads the file, or the shared meeting notes and transcript, from a File added to folder trigger. Pass folderId and eventId from the trigger output. Requires a personal or workspace API key with Workflow API and Knowledge Folder API scopes for files, or Workflow API and Meetings Read API scopes for meetings. Personal meeting notes are never returned.
- Revoke knowledge access

  Removes one person's or workspace API key's direct access to a Langdock knowledge base, by user ID or API key ID. To find a person's user ID from their email, use Find user first. The knowledge base owner's access cannot be removed. For a person, the call succeeds even if they had no direct access, and access through a group or workspace-wide share stays. To downgrade someone from Editor to Viewer instead, use Change knowledge access. The connection's key needs the KNOWLEDGE_FOLDER_API scope and Editor access on the knowledge base.
- Search knowledge

  Performs semantic search across all knowledge folders shared with the API key. Returns relevant document chunks ranked by similarity. Requires KNOWLEDGE_FOLDER_API scope.
- Update action

  Updates an existing action's name, description, code, input fields, or confirmation requirement on a custom workspace integration (public: false). Does not apply to built-in catalog integrations.
- Update agent

  Updates an existing agent's configuration. Only provided fields are changed; omitted fields stay unchanged. Updates the draft only; use the publish agent action to make the changes active. Requires ASSISTANT_API scope.
- Update integration

  Updates the name, description, or icon of an existing custom workspace integration (public: false). Requires INTEGRATION_API scope. Does not apply to built-in catalog integrations.
- Update integration auth

  Updates the authentication configuration of a custom workspace integration (public: false). Does not apply to built-in catalog integrations. Warning: changing authType deletes all existing user connections.
- Update knowledge base

  Renames a Langdock knowledge base or changes its description. Only the sent fields change. This does not touch the files inside; to replace a file use Update knowledge file. The connection's key needs the KNOWLEDGE_FOLDER_API scope and Editor access on the knowledge base.
- Update knowledge file

  Replaces an existing file in a knowledge folder with a new version. The old file is removed and the new file is processed and embedded. Requires KNOWLEDGE_FOLDER_API scope.
- Update skill

  Updates a skill's name, slug, description, instructions, or attached integrations
- Update trigger

  Updates an existing trigger's name, description, polling code, or input fields on a custom workspace integration (public: false). Does not apply to built-in catalog integrations
- Update workflow

  Updates workflow metadata or the draft graph for a workflow the API key can edit. Send the full graph right after Create workflow, and use patch to add, change, or remove individual nodes and edges later. Look up IDs a step needs first: integrations with List integrations, their actions and triggers (both built-in and custom) with Get integration or Get action, connections with List connections, and agents with List agents. Use placeholder (add) steps only when an integration or action is not available in the workspace. Updating the draft does not publish a new version. Send either metadata or one graph update, not both. Requires WORKFLOW_WRITE_API scope and editor access. Always pass the returned review notices on to the user: the workflow has to be checked in the builder, where connections are chosen.
- Upload attachment

  Uploads a temporary file for use in agent conversations. The returned attachment ID can be referenced in chat messages. For permanent, searchable documents use upload file to knowledge folder instead. Requires KNOWLEDGE_FOLDER_API scope.
- Upload knowledge file

  Uploads a file to a knowledge folder for permanent storage and semantic search. The file is processed, embedded, and made searchable across the workspace. For temporary conversation-scoped files use upload attachment instead. Supported types: PDF, Word, text, markdown, HTML, PowerPoint. Requires KNOWLEDGE_FOLDER_API scope.

## Trigger für Langdock

Ein Trigger startet einen Workflow, sobald in Langdock etwas passiert.

- File added to folder

  Starts when a file or meeting is uploaded or moved into the selected Library folder. Existing contents and edits do not trigger. Connect a personal or workspace API key with Workflow API scope. Personal keys use their owner's folder access. Workspace keys can access folders shared with the key or everyone in the workspace. Use Read folder file for the file, or Get meeting with meetingId for owner, attendees, notes, and transcript.
- New user

  Triggers when a workspace user matches one of the selected membership statuses: invited, active, or access requested. Requires USER_MANAGEMENT_API scope and an admin API key.

## Agenten-Vorlagen mit Langdock

- [Integration Builder Agent (Langdock) (auf Englisch) Specialist agent for building, debugging, and managing custom Langdock integrations end-to-end.](https://langdock.com/templates/integration-builder-agent-langdock)

## Einrichtung und Berechtigungen

Eine Action kann nach deiner Bestätigung fragen, bevor sie ausgeführt wird. In einem Agenten steht jede Action auf „Immer erlauben“ oder „Braucht Bestätigung“.

### Dokumentation

- [Integrationen nutzen](https://docs.langdock.com/de/using-langdock/guides/integrations/using-integrations)
- [So funktionieren Verbindungen](https://docs.langdock.com/de/using-langdock/integrations/connections)
- [Zugriff auf Actions verwalten](https://docs.langdock.com/de/admin/manage-integrations/manage-action-access)

[Alle Integrationen](https://langdock.com/de/products/integrations)
