Integration
Connect FieldAware to Browserbase
When New job completed fires in FieldAware, your agent runs Fetch page in Browserbase. 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 FieldAware and Browserbase 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 FieldAware can start in Browserbase
When New job completed in FieldAware
then Fetch page in Browserbase
When New job completed in FieldAware
then Add context in Browserbase
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 FieldAware and Browserbase
Triggers and actions 1 trigger · 47 actions
Trigger
New job completedPolls for jobs that have reached the Completed state. Dedupe on each job's uuid.
Action
Add invoiceCreates an invoice for one or more completed jobs for a customer, with its line items and totals.
Action
Create assetCreate an asset. name and a location UUID are required.
Action
Create contactCreate a contact.
Action
Create customerCreate a customer. name and a location object are required.
Action
Create jobCreate a new job. scheduledOn is required; location is a UUID reference.
Action
Create locationCreate a location. Provide either name+lat+lng or street+locality.
Action
Delete assetDelete an asset by UUID.
Action
Delete contactDelete a contact by UUID.
Action
Delete customerDelete a customer by UUID.
Action
Delete jobDeletes a job from FieldAware.
Action
Delete locationDelete a location by UUID.
Action
Get assetRetrieve a single asset by UUID.
Action
Get contactRetrieve a single contact by UUID.
Action
Get customerRetrieve a single customer by UUID.
Action
Get invoiceRetrieve a single invoice by UUID or invoice number.
Action
Get itemReturns one item (product) by its ID, including its pricing, tax settings and custom fields.
Action
Get jobRetrieve a single job by its UUID.
Action
Get locationRetrieve a single location by UUID.
Action
Get taskRetrieve a single task by UUID.
Action
Get userRetrieve a single user by UUID.
Action
List assetsList all assets.
Action
List contactsList all contacts.
Action
List customersList all customers.
Action
List invoicesList invoices, optionally filtered by createdOn date range.
Action
List itemsList all items (products/services in the catalog).
Action
List jobsList jobs in a date range, optionally filtered by state.
Action
List locationsList all locations.
Action
List tasksList all tasks.
Action
List usersList all users.
Action
Update assetUpdate an asset.
Action
Update contactUpdate a contact.
Action
Update customerUpdate a customer. Fields other than location are optional.
Action
Update invoiceUpdates an existing FieldAware invoice's comments, customer, contact, invoiced jobs, totals or custom fields.
Action
Update itemUpdates an existing item (product) in FieldAware, such as its name, pricing, part number or tax settings.
Action
Update locationUpdate a location.
Action
Add contextCreates a new browser Context that persists cookies and storage across Browserbase sessions.
Action
Add sessionCreates a new Browserbase browser session and returns its id along with the URLs used to connect to it.
Action
Delete contextDeletes a browser context (saved cookies and browser state) from your Browserbase project.
Action
Fetch pageFetches a web page through Browserbase and returns its content (raw, markdown, or schema-extracted JSON), status code and headers.
Action
Get contextReturns a Browserbase context (saved browser state) by its id, including its name, project and timestamps.
Action
Get runReturns the current status and details of an agent run, including its result and the browser session it used.
Action
Get sessionReturns a Browserbase browser session, including its status, region, timestamps and connection URLs.
Action
List downloadsReturns the files downloaded during a Browserbase session, optionally filtered by filename, MIME type, size or creation time.
Action
List sessionsReturns the browser sessions in your Browserbase project, optionally filtered by status or by user metadata.
Action
Run agentStarts a Browserbase browser agent run that completes a natural-language task using web search and browser tools. Returns the new run, which starts in a pending state.
Action
Search webRuns a web search through Browserbase and returns the matching pages with their titles and URLs.
Action
Update sessionUpdates a Browserbase session, such as requesting that it be released before its timeout to stop further charges.
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 FieldAware
FieldAware to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FieldAware to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FieldAware to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FieldAware to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FieldAware to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FieldAware to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Browserbase
HubSpot to BrowserbaseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to BrowserbaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to BrowserbaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to BrowserbaseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to BrowserbaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to BrowserbaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
FieldAware and Browserbase, answered
What can start an automation from FieldAware?
Any of FieldAware's 1 trigger in the catalog, including New job completed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Browserbase when something happens in FieldAware?
Any of Browserbase's 12 actions, including Update session, Add context, Add session and Fetch page. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Browserbase to FieldAware?
Browserbase has no triggers in the catalog today, so automations start in FieldAware. If you need the other direction, ask: your agent reads Browserbase's API documentation and adds it.
Do I have to build a connector for FieldAware or Browserbase?
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 FieldAware and Browserbase 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.