Integration
Connect Pipefile to Browser Use
When something happens in Pipefile, 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 Pipefile 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 Pipefile can start in Browser Use
When File Request Created in Pipefile
then List workspace files in Browser Use
When File Request Created in Pipefile
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 Pipefile and Browser Use
Triggers and actions 1 trigger · 20 actions
Trigger
File Request CreatedTriggers when a file request is created.
Action
Add File Request From TemplateCreate a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
Action
Create ContactAdd to contacts
Action
Delete ContactDelete a contact by id. Returns 204 No Content on success.
Action
Get ContactRetrieve one contact by id.
Action
Get File RequestRetrieve detailed information about one file request by id, including contents, items, files, and tracking events.
Action
List ContactsRetrieve a paginated list of contacts, filterable by name/email/phone partial match.
Action
List File Request TemplatesRetrieve the list of file request templates available for creating new file requests, with optional name search.
Action
Search File RequestsFinds all file requests matching this search query (contact name, email, tags, etc).
Action
Send RequestCreate and send a new request
Action
Update ContactUpdate name/email/phone of an existing contact by id.
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 Pipefile
Pipefile to Google AnalyticsGoogle Analytics tracks and reports website traffic, user behavior, and conversion data, enabling marketers...
Pipefile to ChannelsChannels is a data-driven phone system that lets you make and take calls directly in the browser.
Pipefile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pipefile to StripeStripe is a payment processing platform for online businesses.
Pipefile to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
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
Pipefile and Browser Use, answered
What can start an automation from Pipefile?
Any of Pipefile's 1 trigger in the catalog, including File Request Created. 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 Pipefile?
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 Pipefile?
Browser Use has no triggers in the catalog today, so automations start in Pipefile. 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 Pipefile 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.