Integration
Connect Zite to Browser Use
When New Field fires in Zite, 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 Zite 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 Zite can start in Browser Use
When New Field in Zite
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 Zite and Browser Use
Triggers and actions 9 triggers · 22 actions
- Deleted Field
Triggers when a field is deleted from a table.
- Deleted Record
Triggers when a record is deleted from a table.
- Deleted Table
Triggers when a table is deleted from a base.
- New Field
Triggers when a new field is created in a table.
- New Record
Triggers when a new record is created in a table.
- New Table
Triggers when a new table is created in a base.
- Updated Field
Triggers when a field is updated in a table.
- Updated Record
Triggers when an existing record is updated in a table.
- Updated Table
Triggers when a table is updated in a base.
- Create Field
Creates a new field in a table.
- Create Record
Creates a new record in a table.
- Create Table
Creates a new table in a base.
- Delete Field
Deletes a field from a table.
- Delete Record
Deletes a record from a table.
- Delete Table
Deletes a table from a base.
- Find Field
Finds a field by name.
- Find Record
Finds a record by field value.
- Find Table
Finds a table by name.
- Update Field
Updates a field's name or settings.
- Update Record
Updates an existing record in a table.
- Update Table
Updates a table's name or description.
- 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 Zite
Zite to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Zite to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Zite to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Zite to AnthropicAnthropic builds Claude, a family of large language models.
Zite to GoHighLevelAll-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...
Zite to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
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
Zite and Browser Use, answered
What can start an automation from Zite?
Any of Zite's 9 triggers in the catalog, including New Field, New Record, New Table and Updated Field. 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 Zite?
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 Zite?
Browser Use has no triggers in the catalog today, so automations start in Zite. 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 Zite 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.