Accept Greeting
Accept an incoming LiveChat greeting for an existing customer and mark that greeting as seen in the customer's live session. This changes greeting state.
Manage LiveChat agents, groups, bots, webhooks, properties, and customer conversations through server-side OAuth.
Accept an incoming LiveChat greeting for an existing customer and mark that greeting as seen in the customer's live session. This changes greeting state.
Approve a licensed LiveChat agent so they can use the application. This non-public operation requires the private subscription.lc:rw grant and changes the agent's approval state; do not retry it automatically.
Cancel an incoming LiveChat invitation for an existing customer. This changes the greeting state in the customer's live session.
Read which current organization resources exceed a selected LiveChat plan's limits. This action requires the private subscription.lc:rw grant, which cannot be configured for ordinary public OAuth clients.
Create a normal-role licensed LiveChat user who must await approval. This safe baseline may consume a paid seat and send an irreversible account or approval email. Do not retry after an uncertain outcome. Use Create Privileged Agent only for approval bypass or an elevated role.
Add an ordered LiveChat auto-access rule. The rule immediately changes which groups customers matching its conditions can access.
Create a LiveChat bot and return its write-once secret. Treat the secret as a credential and never log or replay it. The bot does not receive chats until its routing status is set; clean up only through a controlled lifecycle.
Create a bot template for an application client ID and return its write-once secret. Treat the secret as a credential. This affects only the template and future installations; it does not create bots on existing installations.
Create a LiveChat bot template and also create a bot from it on every license where the app is already installed. This is a cross-license bulk creation and returns a sensitive write-once template secret.
Create a group-owned LiveChat canned response. LiveChat sanitizes its text, and is_private controls whether other users can see it.
Create a LiveChat greeting with trigger rules and optional rich content. An active greeting can immediately appear to matching visitors; use active=false while safely preparing it.
Create a LiveChat routing group with its initial language and agent-priority map.
Create a licensed LiveChat agent while explicitly bypassing approval and/or assigning an elevated administrator or viceowner role. This may consume a paid seat, send an irreversible account or approval email, and uses stronger or private grants than Create Agent. Do not retry after an uncertain outcome.
Create a LiveChat tag and optionally assign it to groups. Tag-name duplicate matching is case insensitive.
Deactivate a LiveChat chat by closing its currently open thread. This takes effect immediately and prevents further messages to that thread. Use only for an explicitly selected chat; do not repeat after an uncertain outcome.
Permanently delete a licensed LiveChat agent. This irreversible operation removes the user from the license; verify the exact agent ID and do not retry automatically.
Permanently delete an auto-access rule. This immediately changes customer access routing and should only target a confirmed rule ID.
Permanently delete a LiveChat bot. This irreversible operation can remove a bot from live routing; use an explicit verified bot ID and do not retry automatically.
Permanently delete only a bot template. Bots already installed from the template on existing licenses are not deleted.
Permanently delete a LiveChat bot template and every bot installed from it across all licenses. This cross-license bulk deletion can disrupt live routing and must not be retried automatically.
Permanently delete one canned response by ID, removing it from agent use. Use only a confirmed disposable or intentionally retired response.
Permanently delete selected registered property values from a live customer chat. Property data may contain PII; this action does not retry.
Delete one event from a specified LiveChat chat and thread. This is an irreversible customer-visible action: Customer Chat API responses hide the event, while Agent Chat can retain it as deleted or visible to elevated roles. Use only captured IDs from a disposable lifecycle and do not repeat after an uncertain outcome.
Permanently delete selected registered property values from a live customer-chat event. Property data may contain PII; this action does not retry.
Permanently delete a greeting, immediately stopping it from appearing to new matching visitors. Use only a confirmed disposable or retired greeting ID.
Permanently delete one LiveChat group by ID.
Delete selected custom property values from one LiveChat group without unregistering their definitions.
Delete selected license-level custom property values without unregistering their definitions.
Permanently delete the exact case-sensitive LiveChat tag, removing it from workflows that rely on that tag. Use a confirmed disposable or retired name.
Permanently delete selected registered property values from a live customer-chat thread. Property data may contain PII; this action does not retry.
Disable all webhooks across the connected LiveChat license. Warning: this causes a license-wide webhook outage that persists through application reinstall.
Enable webhooks across the connected LiveChat license after they were explicitly disabled. Warning: this changes license-wide integration state and should not be treated as a guaranteed safe rollback without owner approval.
Trigger LiveChat goal evaluation for an offline customer. Achieved goals can record conversions and trigger configured integrations from the supplied session fields, group, and page URL.
Return one LiveChat agent by ID, including any explicitly requested optional fields.
Return one LiveChat bot by ID with explicitly requested optional fields.
Return the customer profile for an explicit existing LiveChat entity through the server-side customer authorization bridge.
Return one existing customer's LiveChat chat and either its latest thread or a specified thread.
Return versioned forms, buttons, integrations, and readable properties for a LiveChat customer group.
Return the enabled pre-chat or post-chat form for one LiveChat group.
Return versioned customer-facing localization phrases for a LiveChat group and language through LiveChat's public Customer Chat endpoint.
Return current customer-facing widget availability and the version identifiers needed for detailed configuration and localization reads.
Get one LiveChat greeting, including its rules and rich-message structure.
Return one LiveChat group by ID, including any explicitly requested optional fields.
Return whether webhook delivery is enabled for the connected LiveChat license.
Return whether a new chat for an existing customer is predicted to queue and the agent predicted to receive it, when available.
Return the source parameters supplied when the Text product was activated.
Return LiveChat-hosted preview image URLs for a public webpage without changing chat state.
Issue a sensitive, non-revocable bot bearer token valid for 24 hours. The request secret and returned token must never be logged, stored in fixtures, or replayed; this action performs one request with no automatic loop.
List LiveChat agents, optionally filtering by group membership or suspension state.
List every bot in the LiveChat license, including bots not owned by the connected app. This is a privileged license-wide inventory read.
Return one page including every private canned response across the requested LiveChat groups. This privileged read exposes private records beyond those normally accessible to the caller and never fetches later pages automatically.
List all LiveChat auto-access rules in their evaluation order.
List bot templates owned by a specified OAuth application client ID.
List only bots owned by the connected LiveChat app. Use List All Bots for the privileged license-wide inventory.
Return one page of canned responses accessible to the caller and a next_page_id for explicit continuation. This action never reads every private response or fetches subsequent pages automatically.
List summaries of communication channels used by the connected Text product.
List all active customer bans. Results can contain sensitive IP addresses and customer identifiers and should not be persisted unnecessarily.
List threads from one existing customer's chat through LiveChat's server-side customer authorization bridge, returning one page at a time.
List one existing customer's chat summaries through LiveChat's server-side customer authorization bridge, returning one page at a time.
Read the custom property values a customer may access for one LiveChat group. Property values may contain customer data. Warning: live probes of this documented public endpoint currently return HTTP 405 or unsupported action; call it only to check whether provider support has been restored.
Return chat availability statuses for selected LiveChat groups or all groups visible to an existing customer.
Read the license property values visible to a LiveChat customer. Property values may contain customer data. Warning: live probes of this documented public endpoint currently return HTTP 405 or unsupported action; call it only to check whether provider support has been restored.
List a bounded page of LiveChat greetings, optionally filtered by group. Use the returned native next_page_id in a later call when present.
Read group-level property values for selected LiveChat groups or a property namespace.
List all LiveChat groups, optionally requesting additional fields for each group.
Read license-level property values, optionally narrowed to a namespace and property-name prefix.
List private and public LiveChat property definitions owned by a specified OAuth application client ID.
List LiveChat tags, optionally filtering by nested group IDs.
List webhook actions supported by LiveChat Configuration API version 3.6, including their accepted filters and additional payload data.
List webhooks registered for a specified OAuth application client ID.
Advance an existing customer's seen state in a LiveChat chat through an RFC 3339 timestamp. This emits a read-receipt state change for the chat.
Publish a private property for access by tokens belonging to any Client ID. Warning: publication is irreversible; a published property cannot be unpublished or unregistered.
Reactivate a bounced external email address for one LiveChat agent. Warning: this changes external email delivery state and may resume messages to that address.
Register one private custom property definition for a LiveChat OAuth application.
Register one LiveChat webhook endpoint for an OAuth application and action.
Request unsuspension for the connected suspended agent. LiveChat sends external emails to the license owners and vice owners; do not retry this notification operation automatically.
Send a verification email to an existing LiveChat customer. After confirmation, LiveChat sends the verified email to the supplied HTTPS callback exactly once and expects HTTP 200; failed callbacks are not retried.
Request an asynchronous welcome message for an existing logged-in customer. This creates greeting session state, emits incoming_welcome_message later, and can affect AI or agent routing; the response reports the predicted route.
Irreversibly rotate a bot secret and return the sensitive replacement. The old credential stops working; update dependents immediately and never log, persist, replay, or automatically retry this operation.
Irreversibly rotate a LiveChat bot template secret and set the replacement on every installed bot based on it across all licenses. This bulk credential rotation invalidates prior secrets; never log, replay, or automatically retry it.
Irreversibly rotate only a bot template secret and return the sensitive replacement. Existing installed bot secrets are unchanged; never log, replay, or automatically retry this action.
Resume an archived LiveChat chat for an existing customer entity. This is non-idempotent: a successful call creates a new thread and can create initial events, change access or continuous mode, and mark events seen. Do not repeat a call after an uncertain outcome.
Send one event into a real LiveChat chat for an existing customer. This is non-idempotent: a successful call creates and delivers the event and marks chat events seen for the customer. Do not repeat after an uncertain outcome, because duplicate messages or interactions can be delivered.
Upload one non-executable file of at most 10,000,000 bytes and irreversibly deliver it as a file event in an existing LiveChat chat. Delivery also marks chat events seen for the customer. If delivery fails after upload, the temporary uploaded file can remain without an event; do not retry after an uncertain outcome.
Record that an existing customer clicked a specific button in an incoming LiveChat greeting. This writes interaction state for the live session.
Send a button postback for an existing rich-message event. This is non-idempotent and changes the live interaction state; for an active thread it can emit an incoming-rich-message-postback notification. Do not repeat a call after an uncertain outcome.
Send transient typed content into a real LiveChat chat before the customer submits it as a message. Agents may see the supplied text immediately. This is non-idempotent interaction activity; do not repeat after an uncertain outcome.
Replace an existing LiveChat customer's ordered session fields. This mutates customer session/profile data and the values may contain PII.
Start a new LiveChat chat for an existing customer entity. This is non-idempotent: every successful call can create a real chat, thread, and initial events, and it also marks existing chat events seen for the customer. Do not repeat a call after an uncertain outcome.
Suspend a licensed LiveChat agent. This non-public operation requires the private sessions--all:rw grant and can interrupt active sessions and live chat routing; do not retry it automatically.
Lift a customer ban by IP address or customer ID. Warning: this restores the customer's access to the connected LiveChat license.
Permanently remove one custom property definition owned by an OAuth application.
Permanently remove one webhook registration owned by a LiveChat OAuth application.
Unsuspend a licensed LiveChat agent. This non-public operation requires the private subscription.lc:rw grant and restores the agent's ability to participate in live routing; do not retry it automatically.
Update a licensed LiveChat agent. Role, group, login-status, chat-capacity, notification, and schedule changes can immediately alter permissions or live routing; verify the target and intended fields before calling.
Update or reorder an auto-access rule. Changes immediately affect customer access routing, so use a confirmed disposable or intended rule ID.
Update a LiveChat bot. Group, priority, schedule, and chat-capacity changes can immediately alter live routing; verify the bot and intended fields before calling.
Fully replace a LiveChat bot template for future installations. Existing installed bots are not changed. Omitted optional replacement fields are reset or cleared to provider defaults.
Update an existing canned response while preserving omitted fields. Changing its group or privacy setting changes who can access it.
Set registered custom property values on a live customer chat. This mutates chat state and values may contain PII.
Update license-level company details. Warning: this is an organization-wide change, and enrich=true may populate currently empty fields from the company domain.
Partially update an existing LiveChat customer profile. This writes PII and may change omnichannel identity matching; omitted fields remain unchanged.
Set registered custom property values on a live customer-chat event. This mutates event state and values may contain PII.
Update a greeting while preserving omitted fields. Rule, content, or active changes affect matching visitors immediately; deactivate before structural editing when appropriate.
Update the name, language, or complete agent-priority map of an existing LiveChat group.
Set one or more custom property values on a LiveChat group.
Fully replace a LiveChat bot template and propagate the replacement to every bot installed from it across all licenses. Omitted optional replacement fields are reset or cleared to provider defaults. This bulk cross-license update can immediately change live bot routing behavior.
Set one or more license-level custom property values grouped by namespace.
Update a LiveChat tag identified by its exact case-sensitive name. When provided, group_ids replaces the tag's group assignment.
Set registered custom property values on a live customer-chat thread. This mutates thread state and values may contain PII.
Upload one non-executable file of at most 10,000,000 bytes for later use in a Customer Chat event. This creates a temporary provider-hosted file URL that expires after 24 hours unless used in send_event. Do not repeat after an uncertain outcome because each successful call uploads another file.
The LiveChat integration connects your Dench AI CRM directly to LiveChat, so agents can read and act on your LiveChat data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
111 actions are available for agents to invoke on your behalf. Every call runs through LiveChat's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find LiveChat and click Connect — you'll authorize access through LiveChat's own sign-in flow. No API keys or code required.
Ask an agent to use LiveChat in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench LiveChat integration connects your AI CRM to LiveChat, so AI agents can work with your LiveChat data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The LiveChat integration currently exposes 111 actions, including Accept Greeting, Approve Agent, Cancel Greeting, Check Product Limits for Plan, Create Agent, and Create Auto Access. Agents invoke them on your behalf from chat or from automations.
No. You connect LiveChat from your Dench workspace using LiveChat's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through LiveChat's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the LiveChat connection from your workspace settings at any time.