Remote Retrieval

Connect AI agents to Remote Retrieval, a device return service for remote employee offboarding. Agents create device return orders, look up device pricing and company details, and track order status so laptops come back on schedule when employees leave.

Verified 6 actions API key available

Remote Retrieval website ↗ Platform Documentation ↗ Capability data verified 2026-08-10

A termination is recorded in the HR system with a last working day

Agent reads the devices assigned to that employee and their home address

Agent confirms the company profile and default return address on the retrieval account

Agent prices retrieval for each device against the account's device pricing

Agent checks each device against leases, warranty, and any redeployment plan

Agent posts the device list, prices, and the available order types to IT asset management

Asset owner chooses return or recycle for each device before any order is created

What This Integration Enables

Every offboarding checklist has a step that software does not finish: the laptop is in somebody's apartment three time zones away. Remote Retrieval covers that leg, shipping prepaid return kits to remote employees, tracking the outbound and return shipments, and routing recovered devices back to the company or on to a replacement employee. Connecting it to FlowRunner means the physical return starts from the same event that revoked the accounts, rather than from a reminder someone sets and forgets.

The connector's surface is small and honest about it. Agents validate the connection, read the registered company profile and default return address, list per device retrieval pricing available on the account, list and retrieve device return orders with their shipment tracking status, and create an order with the employee and return company details. An order carries an order type of Return To Company or Recycle with Data Destruction, an optional return service of Data Wipe and Return to Company or Data Wipe and Deliver to New Employee, and an optional insured amount. There is no update and no cancel operation, so a created order is a commitment. The vendor also exposes a bulk CSV order endpoint that this connector deliberately does not implement, because its request contract is not published and a connector that guesses at an unverified format is worse than one that leaves it out.

Without FlowRunner

Offboarding stops at the account Access is revoked on the last day and the laptop is chased by email for weeks

Return kits ordered by hand Someone logs into a portal and types the leaving employee's address again

Device fate decided late Whether a machine comes back or gets recycled is settled after it has already sat in a hallway

With FlowRunner

The physical leg is part of offboarding The device return starts from the same termination record that revoked the accounts

Kits ordered from the HR record Employee details flow from the system that already holds them

Device fate decided up front Return, recycle, or redeploy is chosen with prices and lease status visible before the kit ships

Use Case Scenarios

Termination event starts the device return the same day

A termination is recorded in BambooHR or the HRIS of record. The agent reads the leaving employee's assigned equipment and shipping address, calls Get Device Prices to attach a cost to each item, and prepares a draft order. Access revocation, the final payroll task, and the device return all now hang off one event, which is the difference between an offboarding process and an offboarding checklist somebody works through by hand.

Return shipments watched until the device is actually back

Creating the order is not the outcome. The agent polls List Orders and Get Order for the open returns and reads the shipment tracking status on each. Kits that have not been used after an agreed number of days become a nudge to the former employee and a note in the asset record. The report goes into Slack or Google Sheets so the asset register reflects reality rather than intent, which is the thing an auditor eventually asks about.

A device rerouted to the person who needs it next

A replacement hire starts before the leaver's machine is back. Rather than shipping the device to a warehouse and out again, the agent creates the order with the Data Wipe and Deliver to New Employee return service and the new employee's details. The device is wiped in transit and arrives at the person who needs it. The agent fills in the record; the routing decision is confirmed by a human first, for the reason below.

Human-in-Loop Highlight

The gate sits on the order type at Create Order, because one of the two options destroys the asset. Return To Company brings the machine back. Recycle with Data Destruction does what it says, and there is no cancel operation in this API, so once the order exists the kit is on its way. An agent reading an HR termination record can see the employee, the device model, and the price. It cannot see that the machine is on a three year lease with a return obligation, that it is the only place a departing engineer's unbacked local work exists, or that IT already promised it to a new starter. Those facts live in an asset register, a finance system, and somebody's head. So the agent prepares everything and stops: "Rita Alvarez, last day Friday, 2 devices assigned. MacBook Pro 16 retrieval 189 USD, lease ends March 2027. Dell monitor retrieval 74 USD, out of warranty. Order type per device: Return To Company, or Recycle with Data Destruction? Deliver the MacBook to new starter J. Whitfield instead?" A person answers in one message and the agent creates exactly those orders. The routine ninety percent still runs without anyone touching it. The judgment call about destroying a company asset, or shipping a former employee's laptop to a named colleague, stays with a person. That is human-in-the-loop on a decision with no undo.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Account

Validate Connection Confirms the API key is valid and the account is active. Used as a health check before a batch of offboarding orders runs.
Get Company Details Returns the registered company profile and default return address. Used to confirm where recovered devices are sent before an order is built.
Get Device Prices Lists per device retrieval pricing available on the account. Used to attach a cost to each device so the return or recycle decision is made with the number visible.

Orders

List Orders Lists device return orders, cursor paginated. Used to watch open returns and spot kits that have gone unused.
Get Order Retrieves a single order and its shipment tracking status by order id. Used to answer where a specific device is without leaving the workflow.
Create Order Creates a device return order with employee and return company details, an order type of Return To Company or Recycle with Data Destruction, an optional data wipe return service, and optional insurance. Used once a person has confirmed the fate of each device, since there is no cancel operation.

Frequently Asked Questions

What can FlowRunner do with Remote Retrieval?

FlowRunner agents can run Validate Connection, Get Company Details, and Get Device Prices in Remote Retrieval, plus 3 more actions.

Does connecting Remote Retrieval to FlowRunner require OAuth?

No. Remote Retrieval connects to FlowRunner with an API key, no OAuth flow required.

Can Remote Retrieval trigger a FlowRunner workflow automatically?

Remote Retrieval doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Remote Retrieval

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us