Wähle aus 56 verfügbaren Integrationen und 716 nativen Actions, um deine Agenten und Workflows zu erweitern.
Update agent
Updates an existing agent's configuration. Only provided fields are changed; omitted fields stay unchanged. Updates the draft only; a separate publish step (not exposed by this integration) is required to make the changes active. Requires ASSISTANT_API scope.
Update board
Updates a single attribute on a board. Requires a board ID, the attribute to change (name, description, or communication), and the new value. Returns the board ID and confirmation of the update.
Update column
Updates a column's title and/or description on a board (changes the column's schema, not item cell values; for cell updates, use Update item). Requires a board ID, column ID, and at least one of title or description. Returns the column's updated title, type, and description.
Update comment
Updates a comment. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
Update comment
Edit the text of an existing comment. Note: Wrike only allows editing within 5 minutes of creation. Use get_task_comments first to obtain the commentId.
Update comment
Updates an existing comment on a Confluence page. Supports @mentions (resolved to actual users if found, otherwise kept as plain text).
Update contract
Updates fields on an existing Salesforce Contract. To activate a contract, set Status to an Activated-category value (requires the 'Activate Contracts' user permission). Activated contracts cannot have AccountId changed and most fields become read-only without that permission.
Update custom object
Updates properties of an existing custom object record. Use 'Get custom object context' to discover available property names.
Update database
Updates a Notion database's title, description, icon, cover, or property schema. Requires a database ID and at least one field to update. Returns the updated database metadata.
Update draft
Updates an existing draft email by ID. Modify its subject, body, recipients, or attachments.
Update draft
Updates an existing draft email in place. Provide the message ID of the draft and the fields to change — unspecified fields keep their current values.
Update draft in shared mailbox
Updates an existing draft email in a shared mailbox by ID. Modify its subject, body, recipients, or attachments. The draft must already exist in the target mailbox's Drafts folder.
Update element transform
Move, resize, rotate, or shear an existing page element (shape, image, text box, line, group, etc.) on a slide by updating its transform matrix. Use it to reposition or scale elements after creating them or after reading the current layout. Requires the object ID of an element that already exists — get it from the action that created the element (every create action returns the id it used) or from get_presentation (outputFormat "map" or "json"). Never invent or guess the element ID.
Update element z-order
Reorder one or more page elements front-to-back (z-order / stacking order) on a single slide, choosing an operation: BRING_TO_FRONT, BRING_FORWARD, SEND_BACKWARD, or SEND_TO_BACK. Use it to fix overlap - e.g. put a label on top of an image, push a background shape behind text, or bring a highlighted box to the front. All listed elements move together in one atomic batch. This action consumes existing element object IDs: pass the exact objectId of each element (from the create action that returned it, or from get_presentation with outputFormat "map" or "json") - never invent IDs or pass a slide number. Every element must be on the SAME slide and must not be grouped; whole slides and layout-inherited placeholders cannot be reordered. If any ID is wrong the whole batch is rejected and nothing moves.
Update event
Updates an existing calendar event. Supports partial time updates — if only the start time or end time is provided, the other is automatically preserved from the current event. The timezone is required when updating any time field. Use this to directly change event details when the user is the organizer or has edit rights. If the user is an attendee wanting to suggest a different time, use 'Propose new time' instead. Supports shared/delegated calendars: pass a colleague's email in 'Shared calendar owner' to act on their calendar (they must have granted you edit rights); leave it empty for your own calendar.
Update group
Updates a single attribute on a group. Requires a board ID, group ID, the attribute to change (title, color, or position), and the new value. Returns the group's updated ID, title, color, and position.
Update issue
Updates fields on an existing Jira issue such as summary, description, assignee, priority, labels, due date, components, fix versions, or custom fields.
Update item
Updates multiple values of an item. Requires a board ID, item ID, and a columnValues map. Returns the updated item's ID, name, and current column values.
Update item column values
Updates a single column value on an item row in a board. Requires a board ID, item ID, column ID, and the new column value. Returns the updated item's ID.
Update KB article
Update an existing knowledge base article. IMPORTANT: The contentHtml field is mapped to body_html in the API.
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 label
Add/remove labels on a message or a thread. First call 'Get email with attachments' to resolve messageId and/or threadId.
Update line properties
Restyle an EXISTING line, arrow, or connector by changing only the properties you set: color, thickness, dash pattern, arrowheads, or transparency (everything else is left untouched). Use it to edit a line you already added with 'Add line' or any line found in the deck. It does NOT create lines ('Add line') and does NOT move or re-route endpoints ('Update element transform'). ID flow: pass the presentationId from the deck URL plus the line's existing objectId — use the id returned by 'Add line', or look it up via 'Get presentation' (outputFormat "map" or "json"). Never invent or mistype an object ID. The action echoes the line's objectId (as both objectId and lineId) so you can chain further edits.
Update page
Updates a Notion page's properties, icon, cover, or trash status. Also appends content to an existing page: omit blockId and provide blockText with blockType 'markdown' to append a full markdown document of any length, or use a specific blockType (paragraph, heading_1, etc.) for a single block. Provide blockId to update an existing block in place instead. Use this action whenever you need to add content to an existing page.
Update page
Updates an existing Confluence page by ID. Can update title only (efficient) or full content. Use titleChangeOnly=true when users only want to change the page title/heading for token efficiency. Use titleChangeOnly=false for content changes.
Update paragraph style
Formats existing paragraphs in a shape or text box (alignment, line spacing, indentation, space above/below, bullets/numbered lists, and text direction); use it to style copy after the text already exists. Requires two existing IDs: the presentationId from the deck URL and the elementId of the shape/text box. Get elementId from the id returned when the element was created (add_shape_with_text, build_deck_from_outline, etc.) or from get_presentation (outputFormat "map" or "json"); never invent or guess it.
Update record
Updates an existing Dataverse record by GUID. Only the supplied columns are changed; the record is not created if it does not exist.
Update records
Updates column values on an existing record in a single call. Requires a base ID, table name, record ID, and the new field values to update. Returns the updated record.
Update shape properties
Restyle an existing shape's appearance — background fill color/transparency, outline color/weight/dash-style/transparency, and content alignment — in one batch update; use it to polish a shape created by 'Add shape with text' (or any existing shape). Targets an existing shape, so it consumes IDs but creates none: pass the presentationId and the shape's objectId. Supply at least one styling field; fields left blank are unchanged.
Update table
Edits an existing table in a Google Slides presentation in one call: choose ONE operation via the 'operation' field (insert/delete rows or columns, merge/unmerge cells, set cell background fill, set column widths or row heights, or style cell borders) and supply only the inputs that operation needs. Use it after a table already exists (added via 'Add table'). It is index-driven, not ID-driven beyond the table itself: pass the table's object ID plus zero-based row/column indices, never the cell text or a slide number. The presentation is left unchanged if any input is invalid. On success the table's object ID is echoed back so you can chain further edits without re-fetching.
Update task
Updates an existing task's properties (name, assignee, due date, completion status, custom fields, notes). Requires a task GID from search_tasks or typeahead_search. Returns the updated task
Update task
Updates an existing task in a Planner plan. This only works for Planner tasks - for To Do tasks, use the Microsoft To Do integration.
Update task
Update a Wrike task. Supports changing title, description, status, priority/importance, due date, start date, assignees, and custom fields.
Update text style
Formats existing text and/or inserts/replaces text in a shape, text box, or table cell — applying character styles (bold, italic, color, font, size, link, etc.), paragraph styles (alignment, spacing, indentation), and bullet/numbered list formatting. Use after a deck's text elements exist to style or rewrite their content. ID flow: this action consumes the existing element's object ID via objectId — it does not create or return a new element ID. Get objectId from the create action that made the element (add_shape_with_text, add_table, etc. return the id they used) or from get_presentation (outputFormat "map" or "json"); never invent or guess it.
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 file
Uploads a file to OneDrive. Supports files up to 100MB. For files larger than 4MB, uses chunked upload.
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.
Changes in path
Triggers when files are added or modified in a specific path. Useful for CI/CD pipelines, config monitoring, code review automation, or content tracking.
Label changed on email
Triggers when categories are added to or removed from an email in your Outlook mailbox.
New email in shared inbox
Triggers when new emails are received in specified shared inboxes (users you have Mail.Read.Shared access to).
New email in shared mailbox folder
Triggers when emails appear in a specific folder of a shared mailbox (either newly received or moved to it). Requires Mail.Read.Shared permission and folder access.
New email in specific folder
Triggers when emails appear in a specific folder (either newly received or moved to it).
New email matching search
Triggers when new emails matching your search query are received (sent emails excluded unless you add 'in:sent').
New event matching search
Triggers when new calendar events matching the specified search query are created.
New event matching search
Triggers when new calendar events matching the specified search query are created.
New issue
Triggers when a new issue is created in the repository. Does not trigger for pull requests.
New meeting transcript
Triggers when a transcript becomes available for a recently ended Teams meeting.
New message by search
Triggers when a new message is found by searching for a specific keyword or other criteria.
New message in channel
Triggers when a new message was posted in a channel (public, private, DM, etc.).
New message in conversations
Triggers when a new message is posted in a specific conversation (DM, group DM, or channel).
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Actions
Triggers
Fragen & Antworten
Was kann ich mit Langdock‑Integrationen machen?
Integrationen verbinden Langdock mit deinen bestehenden Tools, sodass Agents und Workflows interne Dokumente durchsuchen, Aktionen auslösen, Daten aktualisieren oder Abläufe in deinen Apps automatisieren können.
Welche Tools kann ich mit Langdock integrieren?
Langdock unterstützt eine große Bandbreite gängier Business‑Tools wie Google Drive, Notion, Confluence, Slack, Salesforce, Jira, Asana und viele mehr. Du kannst zudem individuelle Integrationen für jedes Tool erstellen, das eine API anbietet.
Muss ich eigene Integrationen entwickeln?
Das ist nicht notwendig. Die meisten Verbindungen funktionieren sofort nach der Aktivierung. Wenn du jedoch erweiterte Funktionen oder Actions benötigst, bietet Langdock einen integrierten Builder an. Damit erstellst du deine eigene Logik – inklusive unterstütztem JavaScript-Flow.
Sind Integrationen sicher?
Absolut. Langdock nutzt eine sichere Authentifizierung (inklusive OAuth 2.0), verwahrt Zugangsdaten geschützt und führt eigenes Code‑Handling in einer isolierten Sandbox‑Umgebung aus. Zusätzlich ist Langdock ISO 27001‑zertifiziert, SOC 2 Type II-geprüft und vollständig DSGVO‑konform.
Wie nutze ich Integrationen in einem Chat oder Agenten?
Sobald eine Integration verbunden ist, kannst du sie in jedem Chat direkt nutzen, indem du @ eingibst und verfügbare Actions auswählst. Außerdem können Agenten dank ihrer Anweisungen Integrationen automatisch ausführen.
