Integration
Connect Kit to Browser Use
When New Form Subscriber fires in Kit, 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 Kit and Browser Use to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Kit can start in Browser Use
When New Form Subscriber in Kit
then Upload 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 Kit and Browser Use
Triggers and actions 7 triggers · 17 actions
- New Form Subscriber
Triggers when a subscription occurs on a specific form.
- New Purchase
Triggers when a new purchase is added to your account.
- New Sequence Subscriber
Triggers when a subscriber is added to a sequence.
- New Subscriber
Triggers when a new subscriber is confirmed within your account (has completed any applicable double opt-ins).
- New Unsubscribe
Triggers when a subscriber unsubscribes from your emails.
- Subscriber Added to Tag
Triggers when a specific tag is added to a subscriber.
- Tag Removed From Subscriber
Triggers when a specific tag is removed from a subscriber.
- Add Subscriber to Form
Subscribe someone to a specific form.
- Add Tag to Subscriber
Add a subscriber to a specific tag.
- Create or Update Subscriber
Creates a Kit subscriber, or updates the first name and custom fields of an existing subscriber with the same email address. Returns the subscriber.
- Find Subscriber
Finds an existing confirmed subscriber by email.
- Get Subscriber
Returns one Kit subscriber by ID, with their name, email address, state and custom field values.
- List Tags for Subscriber
Lists the tags on a Kit subscriber, with each tag's ID, name and the date it was applied.
- Remove Tag From Subscriber
Remove a specific tag from a subscriber if they have it.
- Add profile
Create a new browser profile (persisted cookies/state) for reuse across runs.
- Add workspace
Create a new workspace for browser automation files and state.
- Delete profile
Delete a browser profile.
- Delete workspace
Delete a workspace.
- Get profile
Get the details of a specific browser profile.
- Get workspace
Get the details of a specific workspace.
- List workspace files
List files stored in a workspace.
- Update profile
Update a browser profile.
- Update workspace
Update a workspace's settings.
- Upload workspace files
Upload 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 Kit
Kit to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Kit to API SnapFree utility API platform. QR codes, screenshots, PDFs, image resize, hashing, and more
Kit to ClayClay is a simple spreadsheet interface, yet powerful automation platform that allows you to build internal...
Kit to ClerkClerk is a user authentication and management platform that lets developers add sign-in, profiles, and...
Kit to GDBrowserGDBrowser is a readable HTTP wrapper over the Geometry Dash game servers.
Kit to PostLakeOne API to publish, schedule, and read analytics across every major social network
More into Browser Use
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Browser UseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Kit and Browser Use, answered
What can start an automation from Kit?
Any of Kit's 7 triggers in the catalog, including New Form Subscriber, New Purchase, New Sequence Subscriber and New Subscriber. 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 Kit?
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 Kit?
Browser Use has no triggers in the catalog today, so automations start in Kit. 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 Kit 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.
Can my AI client use Kit and Browser Use without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.