Langdock Admin: Integration für KI-Agenten
Manage users, groups, roles, governance, audit logs, usage, and billing
Verbinde Langdock Admin mit Langdock und nutze es im Chat, in Agenten und in Workflows.
33 Actions
Beschreibungen, Actions und Beispiel-Prompts kommen direkt aus dem Produkt und sind dort auf Englisch verfasst.
Actions für Langdock Admin
Jede Action ist ein Schritt, den ein Agent oder Workflow in Langdock Admin ausführen kann.
- Add group members
Adds one or more active workspace users to a group by email, with an optional group role (member, editor, or admin). Returns lists of added emails, emails already in the group, and emails not found among active workspace members. SCIM-managed groups cannot be modified. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Create group
Creates a new workspace group with a name and optional description. Returns the created group's ID and metadata. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Deactivate user
Deactivates a workspace member by email. Their workspace access, sessions, and synced folders end and their scheduled automations stop running, while their conversations, agents, knowledge folders, and integrations stay in the workspace. Reactivation requires Langdock support, and the last active admin cannot be deactivated. Requires USER_MANAGEMENT_API scope on an admin-created workspace key.
- Delete group
Permanently deletes a workspace group by ID. SCIM-managed groups cannot be deleted through this endpoint. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Dismiss usage request
Dismisses a pending workspace usage request without changing the requesting member's plan or extra-usage limit. Approving a request is done via update user billing plan or update user extra usage with usageRequestId. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Export usage
Exports workspace usage data for the given date range. Pick the dataset (agents, assistants, API keys, users, workflows, projects, or models) and a from/to range. Returns the records inline, or a CSV download when output format is file. Some datasets accept an optional group by. Requires USAGE_EXPORT_API scope on an admin-created workspace key
- Find user
Finds a workspace user by email, or lists workspace users ordered by email. Returns each user's ID, which other Langdock actions need to share workflows, knowledge folders, or other resources with a person, plus email, name, membership status (active, invited, or accessRequested), workspace role, department, company name, custom instructions setting, default model, and creation timestamp. Invited users have no user ID until they accept the invite. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Get billing agent
Gets a workspace agent's monthly budget (none, unlimited, or limited with amount), budget mode (always or on_limit_hit), and current billing period spend by agent ID. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Get billing group
Gets a workspace group's billing extra-usage limit (in ai-models-included workspaces) or monthly budget (in bring-your-own-keys workspaces), SCIM management flag, and active human member count by group ID. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Get billing settings
Gets the workspace billing mode (ai-models-included or bring-your-own-keys), currency, workspace extra-usage or usage-limit settings, default limits or monthly budgets per plan, current period spend, and seat counts (in ai-models-included mode) or plan counts (in bring-your-own-keys mode). Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Get billing user
Gets a workspace member's billing plan, configured and effective extra-usage limit or monthly budget, and current period spend by user ID. Includes email and name when the API key also has the USER_MANAGEMENT_API scope. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Get governance agent
Gets a workspace agent's governance status, owner, verification status, disabled status and reason, review status, compliance risk roll-up, and per-rule compliance evaluation results. Requires GOVERNANCE_API scope on an admin-created workspace key and Governance enabled on the workspace
- Get group
Gets a workspace group by ID, returning its name, description, SCIM management status, public status, member count, and timestamps. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Get usage request
Gets a workspace usage request by ID, including the requesting user ID (plus email and name when USER_MANAGEMENT_API is enabled), status, timestamps, and resolution details. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Invite users
Invites one or more users to the workspace by email. Existing members are skipped and pending join requests are approved automatically. Requires USER_MANAGEMENT_API scope on an admin-created workspace key.
- List audit logs
Lists workspace audit log events ordered newest-first, with optional filters for time range, entity type, actor ID, and action. Requires AUDIT_LOG_API scope on an admin-created workspace key belonging to the requested workspace
- List billing agents
Lists workspace agents with their monthly budget (none, unlimited, or limited with amount), budget mode (always or on_limit_hit), and current billing period spend. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- List billing groups
Lists workspace groups with their billing extra-usage limit (in ai-models-included workspaces) or monthly budget (in bring-your-own-keys workspaces), SCIM management flag, and active human member count. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- List billing users
Lists active human workspace members with their billing plan, configured and effective extra-usage limit or monthly budget, and current period extra-usage spend. User emails and names are included when the API key also has the USER_MANAGEMENT_API scope. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- List governance agents
Lists workspace agents with their governance review status, compliance risk roll-up, compliance rule evaluation results, and disabled state. Requires GOVERNANCE_API scope on an admin-created workspace key and Governance enabled on the workspace
- List group members
Lists the members of a workspace group ordered by email address, including each member's user ID, email, name, and group role. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- List groups
Lists workspace groups ordered by creation time, or filters for a group by exact name. Returns each group's ID, name, description, SCIM management flag, public flag, member count, and timestamps. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- List roles
Lists workspace system roles (member, editor, admin) and custom roles, including each role's ID, kind, name, and description. Custom role UUIDs can be assigned to members or editors with the update user role action. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- List usage requests
Lists workspace usage requests ordered oldest-first. Includes requester email and name when the API key also has the USER_MANAGEMENT_API scope. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Remove group members
Removes one or more members from a workspace group by email. Returns lists of removed emails and emails that were not members of the group. SCIM-managed groups cannot be modified. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Update agent billing budget
Updates a workspace agent's monthly budget (none, unlimited, or limited with a positive amount) and/or budget mode (always or on_limit_hit). At least one of budgetType or budgetMode must be provided. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Update billing settings
Updates workspace billing and usage-limit settings for the workspace's active billing mode (ai-models-included or bring-your-own-keys). Automatically detects the workspace billing mode and sends the mode-appropriate settings patch. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Update governance agent status
Enable or disable a workspace agent through the Governance API. Requires a workspace API key with the GOVERNANCE_API scope and Governance enabled on the workspace
- Update group
Updates a workspace group's name and/or description. At least one of name or description must be provided. SCIM-managed groups cannot be edited through this endpoint. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
- Update group billing limit
Updates a workspace group's extra-usage limit (in ai-models-included workspaces) or monthly budget (in bring-your-own-keys workspaces) to either a non-negative amount or unlimited. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Update user billing plan
Updates the billing plan for a single workspace member (via userId, with optional usageRequestId to resolve a pending usage request) or for up to 500 workspace members in bulk (via userIds). Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Update user extra usage
Updates a workspace member's individual extra-usage limit (in ai-models-included workspaces: limited, unlimited, or inherit) or extra-usage budget (in bring-your-own-keys workspaces: limited, unlimited, or none), optionally resolving a pending usage request. Requires BILLING_API scope on a workspace key owned by an active Admin service account
- Update user role
Changes the workspace system role (member, editor, or admin) of an active workspace member, identified by email, and optionally updates or clears their assigned custom roles. Leaving Custom role IDs empty without enabling Clear custom roles preserves the member's existing custom roles. Custom roles can only be assigned to members or editors, not admins. The workspace must keep at least one active admin. Requires USER_MANAGEMENT_API scope on an admin-created workspace key
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“.