Integration
Connect ContentStudio to Browser Use
When something happens in ContentStudio, your agent does the next thing in Browser Use. Describe it 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 ContentStudio 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 ContentStudio can start in Browser Use
When List Campaigns in ContentStudio
then Add profile in Browser Use
When List Labels in ContentStudio
then Add workspace 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 ContentStudio and Browser Use
Triggers and actions 5 triggers · 19 actions
Trigger
List CampaignsLists campaigns (folders) in a workspace. Useful for getting campaign IDs to assign to posts.
Trigger
List LabelsLists labels in a workspace. Useful for getting label IDs to assign to posts.
Trigger
List MediaLists media assets in a workspace media library with filtering, search, and sort options.
Trigger
List Team MembersLists team members in a workspace. Useful for getting user IDs for approval workflows.
Trigger
List WorkspacesReturns all workspaces you have access to so you can choose where to post.
Action
Add CampaignCreate a new campaign in a workspace to group posts.
Action
Add LabelCreate a new label for organizing posts.
Action
Delete CampaignDelete a campaign.
Action
Delete LabelDelete a label.
Action
Delete WorkspaceDelete a workspace.
Action
Update CampaignUpdate an existing campaign's details.
Action
Update LabelUpdate an existing label's name or color.
Action
Update WorkspaceUpdate an existing workspace's settings.
Action
Upload MediaUploads a media file from URL into the workspace media library.
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 ContentStudio
ContentStudio to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
ContentStudio to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ContentStudio to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ContentStudio to Google SheetsGoogle Sheets
ContentStudio to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
ContentStudio to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
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
Gmail to Browser UseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Browser UseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ContentStudio and Browser Use, answered
What can start an automation from ContentStudio?
Any of ContentStudio's 5 triggers in the catalog, including List Campaigns, List Labels, List Media and List Team Members. 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 ContentStudio?
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 ContentStudio?
Browser Use has no triggers in the catalog today, so automations start in ContentStudio. 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 ContentStudio 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.