Wähle aus 56 verfügbaren Integrationen und 716 nativen Actions, um deine Agenten und Workflows zu erweitern.
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. Always call Get table schema first to get the exact field names — using incorrect field names will silently fail. 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.
File updated
Triggers when a file is updated in a SharePoint folder. Re-fires each time a file's contents change, and optionally filter by name or file extension.
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 item created
Triggers when a new file or folder is created in a SharePoint folder. Watch files, folders, or both, and optionally filter by name or file extension.
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).
Property changed
Triggers when a property on a HubSpot object (a standard object like a contact, company, deal, or ticket, or a custom object) changes. Watching a specific property fires once per value transition and returns the new value under a key named new_ followed by the property name (e.g. new_dealstage when watching dealstage). Leave the property name empty to fire on any update to the object instead.
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
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.
