Wähle aus 56 verfügbaren Integrationen und 716 nativen Actions, um deine Agenten und Workflows zu erweitern.
Get dashboard
Reads a Databricks (Lakeview) dashboard's metadata, its underlying SQL queries, and page structure. Accepts a dashboard ID or a dashboard URL.
Get database details
Retrieves the schema and metadata of a specific Notion database. Requires a database ID. Returns the database's property definitions, title, and metadata.
Get dataset schema
Gets table and column metadata from a Power BI dataset using the XMLA endpoint. Call this for tables, columns, schema, or table structure. It does not return measures or relationships. The complete catalog is always attached as a JSON file; inline lists are a preview of the first 3 items (and the first 3 columns per table). When the user wants a full semantic model, to describe a dataset including measures and joins, or to ground DAX, also call Get semantic model measures and Get semantic model relationships. Dataset accepts a name, URL, or ID; search_datasets if the name is ambiguous. Requires Premium Per User (PPU), Premium capacity, or Fabric capacity with XMLA endpoint enabled.
Get deal
Gets the full details of a single deal by its ID, with custom fields resolved to their labels.
Get deal context
Gets required information on deal properties, available stages, and the actual property values from a specific deal.
Get deal context
Gets a deal together with its attached products and activities, for a full picture of the deal in one call.
Get email
Gets the full content of a single email by ID and downloads all attachments. Set 'sharedFolderOwner' to the mailbox email address to fetch from a shared mailbox you have access to.
Get email with attachments
Retrieves a single email thread or message with full content including attachments. Returns all messages in the thread and their attachment files.
Get event
Retrieves a specific event by its ID, including attachment metadata (name, type, size) but not file content. Use Get event attachments to download attachment files. 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.
Get event attachments
Downloads file attachments from a calendar event. Use after Get event when you need the actual files. Pass Attachment names to select which files to download; leave empty to download every file that fits the response size limit. Supports shared/delegated calendars via Shared calendar owner.
Get event invitees
Gets the invitees (attendees) of a scheduled event with their name, email, and responses.
Get events for specific date
Retrieves all calendar events for a specific date. Times are automatically displayed in the user's configured timezone. Use this for events on a specific single date like 'what do I have on Friday?' or 'meetings on March 15th'.
Get fields
Returns all Jira fields with schema metadata. Use this to find field IDs (e.g., customfield_12345) and understand their types.
Get fields
Returns all Jira fields with schema metadata. Use this to find field IDs (e.g., customfield_12345) and understand their types.
Get file
Gets / downloads a file from Sharepoint based on the item ID and attaches it to the chat, use this action to get the contents of a file.
Get file content
Retrieves the actual content of a file from a repository. Use get_repository_content first to find the file path, then use this action to read its contents.
Get file content
Retrieves the raw text content of a file in a project's repository. Use Get repository content first to find the path.
Get file metadata
Retrieves detailed metadata for a file by its ID including name, type, size, dates, and owner information.
Get folder by name
Retrieves a folder from OneDrive by its name or path. Supports nested paths like "Parent/Child/Grandchild".
Get folders
Lists folders you can access in UiPath Orchestrator (including Shared, personal workspaces, and Solution folders) and returns their IDs. Use this to discover the folder ID required by other actions — processes published from Studio Web often live under a personal workspace or Solution folder, not Shared.
Get frame items
Retrieves items within a specific frame, up to Limit (default 10). Pages through Miro's API (max 50 per request) until the limit is reached.
Get free/busy for calendar
Retrieves free/busy information for one or more calendars over a specified time range using the Google Calendar API /freeBusy endpoint.
Get Genie response
Gets a Genie response that was still processing when Ask Genie returned. Returns the answer, generated queries, and query results when ready.
Get goal
Gets detailed goal data including due dates and owner. Requires a goal GID from get_goals. Returns full goal details
Get goals
Lists goals in a workspace, optionally filtered by team, project, portfolio, or owner. Requires a workspace GID from list_workspaces. Returns goal GIDs, names, and owners
Get HubSpot owners
Retrieves all HubSpot owners/users with optional filtering by email. Returns owner IDs that can be used in hubspot_owner_id fields when creating or updating contacts, companies, deals, and notes.
Get incident metadata
Gets field definitions for the incident table, including labels, data types, required flags, and allowed values for choice fields. Use this action to discover which fields are mandatory in your ServiceNow instance before creating or updating incidents. Set onlyRequired=true to get only mandatory fields. Custom fields and their requirements vary by instance.
Get index configuration
Returns field configuration for your Kendra index. Shows field names, types (STRING, DATE, LONG), and properties (searchable, sortable, facetable). Run this BEFORE searching to know which fields you can use for filtering and sorting.
Get integration
Retrieves an integration's summary (name, auth type, action/trigger list) by default. Set includeDetails for auth configuration, action code/input fields, and trigger polling code. For a single action's code without loading every action, use get action.
Get items
Gets items from a Monday board. By default, fetches all items on the board. If not specified, get the limit for the board from the get_boards action output, use itemIds to look up specific items by ID across boards, or searchQuery to find items by exact name. Returns an array of items with their ID, name, column values, and file attachment metadata.
Get item updates
Retrieves the comment thread on a specific item. Requires an item ID. Returns a list of updates with author, text content, timestamp, and file attachment metadata on updates and replies.
Get job details
Retrieves full details of a UiPath job for deep troubleshooting, including expanded robot, process release and machine info, input/output arguments, error details, and (by default) the job's execution logs. Use this to investigate why a job behaved a certain way; for a quick status check use check_job_status instead.
Get jobs
Lists jobs in UiPath Orchestrator, optionally filtered by state, process name, and folder. Use to see what's running, find recent failures, or look up a job ID.
Get job statistics
Computes success and failure statistics per automation process over a time window, from UiPath Orchestrator job history. Use to report on automation reliability, e.g. how many jobs succeeded vs failed for a process this month. Each process also lists faultedJobIds (Ids of its Faulted jobs) you can pass to Get job details for root-cause analysis.
Assignee assigned
Triggers when an issue is assigned to someone, and again when it is reassigned to a different person. Optionally scope to a single team.
Call ended
Triggers when a Google Meet call ends, so you can fetch the transcript, send follow-ups, or log the call.
Changed activity
Triggers when an activity is created or updated. You can additionally filter any event to records where a specific field matches given value(s).
Changed deal
Triggers when a deal is created or updated. You can additionally filter any event to records where a specific field matches given value(s) (e.g. Updated with status = won to react to deals becoming won).
Changed lead
Triggers when a lead is created or updated. You can additionally filter any event to records where a specific field matches given value(s).
Changed note
Triggers when a note is created or updated. You can additionally filter any event to records where a specific field matches given value(s).
Changed organization
Triggers when an organization is created or updated. You can additionally filter any event to records where a specific field matches given value(s).
Changed person
Triggers when a person is created or updated. You can additionally filter any event to records where a specific field matches given value(s).
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.
Changes in path
Triggers when files under a specific path change in a project. Useful for docs or config sync workflows.
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.
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.
Issue state changed
Triggers when an issue moves to a different workflow state (e.g. Todo to In Progress, or In Progress to Done). Does not fire on issue creation. Optionally scope to a single team or workflow state.
Job ended
Triggers when a UiPath Orchestrator job reaches a terminal state (Successful, Faulted, or Stopped). Use to react to finished automations, for example to notify on failures or to process a job's output once it completes.
Label changed on email
Triggers when categories are added to or removed from an email in your Outlook mailbox.
Label changed on email in shared inbox
Triggers when categories are added to or removed from an email in a shared inbox (an owner you have Mail.Read.Shared access to).
New automation idea
Triggers when a new automation idea is created or submitted in Automation Hub. Event data includes newPhase / newStatus (initial pipeline values). Optionally filter by phase, status, category, or application.
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).
New message with tag
Triggers when a specific user is @-mentioned in a Viva Engage community, in either a thread starter or a reply.
New reaction in channel
Triggers when someone reacts to a channel message or a reply in its thread. Optionally filter to one reaction type (Unicode emoji like 👍, or a display name like Like). Requires ChannelMessage.Read.All on the connection (granted when a channel-message action such as Get channel messages is enabled).
New reaction in chat
Triggers when someone reacts to a message in a Teams chat (1:1 or group). Optionally filter to one reaction type (Unicode emoji like 👍, or a display name like Like). Requires Chat.ReadWrite on the connection (granted when a chat-message action such as Get chat messages is enabled).
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.
Updated automation idea
Triggers when an automation idea is updated (phase/status moves or other edits). Does not fire on create. Event data includes newPhase / newStatus (current values after the update); oldPhase / oldStatus are null because the Open API does not expose prior values. To watch ideas going Live, set Phase ID to your tenant's Live phase ID from a Search automation ideas card.
Updated issue
Triggers when an existing Jira issue is modified (e.g., status change, field edit, reassignment). Does not fire for newly created issues — use "New issue" for that.
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
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.
