Integration
Connect LiveAgent to Browser Use
When New conversation fires in LiveAgent, your agent runs Upload workspace files in Browser Use. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want LiveAgent and Browser Use to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What LiveAgent can start in Browser Use
When New conversation in LiveAgent
then Upload workspace files in Browser Use
When New Customer in LiveAgent
then List workspace files in Browser Use
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with LiveAgent and Browser Use
Triggers and actions 3 triggers · 17 actions
Trigger
New conversationTriggers when a new conversation (ticket, chat, call or message) is created in LiveAgent.
Trigger
New CustomerTriggers when a new customer (contact) is added in LiveAgent.
Trigger
New Customer (Experimental)Triggers when a new customer (contact) is added in LiveAgent.
Action
Add customer groupCreates a new customer group in LiveAgent with a name and optional text and background colors.
Action
Add tagCreates a new tag in LiveAgent that can be assigned to conversations.
Action
Get conversationReturns a LiveAgent conversation (ticket) by its ID, code or public URL code, including status, owner, tags and custom field values.
Action
List conversation messagesReturns all message groups and their messages for a LiveAgent conversation, optionally limited to a date range.
Action
List conversationsReturns conversations (tickets, chats, calls) in LiveAgent, optionally filtered by owner, department, agent, status, channel, subject and dates.
Action
List customer groupsReturns every customer group defined in the LiveAgent account, with each group's id and name.
Action
List tagsReturns every tag defined in the LiveAgent account, with each tag's id and name.
Action
Add profileCreate a new browser profile (persisted cookies/state) for reuse across runs.
Action
Add workspaceCreate a new workspace for browser automation files and state.
Action
Delete profileDelete a browser profile.
Action
Delete workspaceDelete a workspace.
Action
Get profileGet the details of a specific browser profile.
Action
Get workspaceGet the details of a specific workspace.
Action
List workspace filesList files stored in a workspace.
Action
Update profileUpdate a browser profile.
Action
Update workspaceUpdate a workspace's settings.
Action
Upload workspace filesUpload files into a workspace.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from LiveAgent
LiveAgent to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LiveAgent to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LiveAgent to MailchimpMailchimp marketing automation and email platform.
LiveAgent to StripeStripe is a payment processing platform for online businesses.
LiveAgent to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LiveAgent to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Browser Use
Webflow to Browser UseWebflow is a professional website builder and CMS for designing, building, and launching responsive...
HubSpot to Browser UseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Browser UseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Browser UseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Browser UseGoogle Sheets
Gmail to Browser UseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
LiveAgent and Browser Use, answered
What can start an automation from LiveAgent?
Any of LiveAgent's 3 triggers in the catalog, including New conversation, New Customer and New Customer (Experimental). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Browser Use when something happens in LiveAgent?
Any of Browser Use's 10 actions, including Update profile, Update workspace, Upload workspace files and Add profile. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Browser Use to LiveAgent?
Browser Use has no triggers in the catalog today, so automations start in LiveAgent. If you need the other direction, ask: your agent reads Browser Use's API documentation and adds it.
Do I have to build a connector for LiveAgent or Browser Use?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.