Integration
Connect Quipu to Browser Use
When New Contact fires in Quipu, 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 Quipu 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 Quipu can start in Browser Use
When New Contact in Quipu
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 Quipu and Browser Use
Triggers and actions 2 triggers · 30 actions
- New Contact
Triggers when a new contact is added in Quipu.
- New Invoice
Triggers when a new invoice is created in Quipu.
- Create Contact
Creates a contact (client, supplier or employee) in Quipu.
- Create Numbering Series
Creates a numbering series for invoices or other documents.
- Delete Contact
Deletes a contact.
- Delete Invoice
Deletes an invoice.
- Find Contacts
Finds contacts by kind, tax ID, email, country or free text.
- Get Contact
Returns one contact by its ID.
- Get Invoice
Returns one invoice by its ID.
- Get Simplified Invoice
Returns one simplified invoice (ticket) by its ID.
- List Accounting Categories
Lists the accounting categories (income and expense accounts).
- List Accounting Subcategories
Lists the accounting subcategories.
- List Additional Incomes
Lists additional incomes.
- List Book Entries
Lists all book entries (invoices, tickets, paysheets and other documents).
- List Economic Activities
Lists the business's economic activities (IAE).
- List Invoices
Lists invoices, filtered by kind, contact or date period.
- List Liquidations
Lists liquidations: payments matched to documents.
- List Money Accounts
Lists bank and cash accounts.
- List Money Entries
Lists bank and cash movements.
- List Numbering Series
Lists the numbering series used to number documents.
- List Paysheets
Lists paysheets.
- List Simplified Invoices
Lists simplified invoices (tickets), filtered by kind, contact or period.
- 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 Quipu
Quipu to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Quipu to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Quipu to StripeStripe is a payment processing platform for online businesses.
Quipu to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Quipu to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Quipu to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
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.
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
Quipu and Browser Use, answered
What can start an automation from Quipu?
Any of Quipu's 2 triggers in the catalog, including New Contact and New Invoice. 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 Quipu?
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 Quipu?
Browser Use has no triggers in the catalog today, so automations start in Quipu. 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 Quipu 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 Quipu 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.