Introducing Browser Automation

Not every website was built for AI

Every supply chain depends on more than its systems of record. Operators spend their days moving between carrier portals, customer websites, appointment scheduling systems, government portals, and supplier applications to complete their work.

Pallet already connects to modern enterprise systems through APIs and EDIs and legacy systems through native AS/400 support and Remote Desktop environments, but one major category of enterprise software has remained out of reach for AI: browser-based applications.

These applications were built as user interfaces. They assume a person will log in, search, download, submit, and update. They weren’t designed for another application to consume information or perform actions programmatically.

Some expose APIs. Many don’t. Even when APIs exist, they often cover part of the workflow. Shipment status might be available through an API, while appointment scheduling, document retrieval, booking updates, or other operational tasks can only be completed through the website itself.

For years, those browser-only workflows required manual work.

That assumption is no longer true.

Pallet Agents can now operate browser-based applications

Pallet Agents can now securely log into browser-based applications and work through the existing web interface, just as an operator would.

Agents can navigate websites, retrieve shipment information, complete forms, download documents, submit transactions, and verify that each action was completed successfully before moving to the next step. Rather than requiring every application to expose an API or building a custom integration for every portal, Pallet Agents work directly through the interface organizations already use.

For IT teams, Browser Automation removes another common deployment bottleneck. Some applications expose robust APIs, others expose only part of the workflow, and many expose none at all. Rather than forcing every application into a single integration model, Pallet Agents use the interface that's already available, allowing organizations to deploy AI without waiting on software vendors or building custom connectors.

This follows a principle that has guided how we build Pallet: businesses shouldn't have to change the systems they rely on before they can deploy AI. Whether a workflow is available through an API, an AS/400 system, a Remote Desktop environment, or simply a browser, agents should be able to work wherever the business already operates.

From email to carrier portals, without human handoffs

Many enterprise workflows begin in one system and end in another.

A customer emails asking where a shipment is. An operator opens a carrier portal, searches the tracking number, reviews the latest milestone, updates the TMS, and replies to the customer.

Historically, a person had to bridge those systems manually.

Pallet Agents can now execute the full workflow from beginning to end. Whether the work happens through an API, EDI connection, browser, AS/400 terminal, Remote Desktop environment, or enterprise application, the agent can move between environments and complete the necessary actions.

Examples include:

• Track and trace: Retrieve shipment milestones from carrier portals such as Maersk, SAIA, and other transportation providers when APIs aren't available, then automatically update internal systems or notify customers.
• Appointment scheduling: Log into customer appointment portals, submit appointment requests, capture confirmations, and update the TMS.
• Booking management: Access ocean carrier portals to confirm bookings, retrieve sailing schedules, and download shipping documents.
• Document retrieval: Download proofs of delivery, invoices, delivery receipts, customs documents, and other files from customer or carrier websites, then route them into downstream workflows.
• Order updates: Read information from emails, enter updates into customer portals, and verify submissions without requiring an operator to switch between applications.

Agents handle repetitive browser work from beginning to end while escalating unfamiliar page layouts, unexpected website changes, or business exceptions to operators when human judgment is required.

Browser-only workflows are no longer a barrier to AI

For years, browser-based applications without complete APIs forced organizations to rely on manual work or expensive one-off integrations.

With Browser Automation, Pallet Agents can now execute workflows across APIs, browser-based applications, AS/400 systems, Remote Desktop environments, and enterprise software as a single workflow.

No matter where information lives, whether in a TMS, a carrier portal, a customer website, or a legacy system, Pallet agents can move between each environment and complete the work from beginning to end.

See Browser Automation in action today.