# Create Revivn Asset Retrieval

Submit a device-return request to Revivn from a runbook

Submits a device-return (asset retrieval) request to [Revivn](https://revivn.com) from a runbook — typically the last step of an offboarding or device-swap flow. The agent collects the device details and the employee's shipping address in conversation, then this tool files the retrieval with Revivn.

## How It Works

1. The agent gathers, in conversation, the **asset(s) being returned** and the **employee's shipping address**.
2. The tool submits the retrieval request to Revivn with those details.
3. Everything else — where devices are shipped, how the retrieval is paid for, insurance — comes from the tool's configuration, not the conversation, so employees can't change it.

## Configuration

In the Risotto dashboard, select **Tools** in the sidebar. Select **Revivn** in the **Tool groups** list. Find **Revivn Create Asset Retrieval V1** and click **Set up**. Fill in these settings, then click **Save**:

| Setting              | Required                     | Description                                                                                                                                            |
| -------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Host**             | Yes                          | Revivn API base URL: `https://api.revivn.com` (production) or `https://api.revivn.dev` (sandbox).                                                      |
| **Client Id**        | Yes                          | OAuth2 client ID issued by Revivn.                                                                                                                     |
| **Client Secret**    | Yes                          | OAuth2 client secret issued by Revivn. Stored encrypted.                                                                                               |
| **Direct To Revivn** | No                           | When enabled, devices ship directly to Revivn and the return recipient is ignored. Disabled by default.                                                |
| **Return Recipient** | When Direct To Revivn is off | The full shipping address (name, company, email, street, city, state, zip, country) that returned devices are sent to, typically your IT depot.        |
| **Payment Method**   | Yes                          | How Revivn charges for the retrieval: **earnings** (uses your available Revivn earnings) or **payment** (charges the Stripe card on file with Revivn). |

> **Tip:** Test against the sandbox host (`https://api.revivn.dev`) with sandbox
> credentials before pointing the tool at production — retrievals created in
> production are real shipping orders.

## Example Runbook Uses

- **Offboarding**: after IT confirms the departure, collect the employee's home address and file the laptop retrieval automatically
- **Device swap**: when a replacement device ships, create the retrieval for the old one in the same conversation

## Troubleshooting

### Authentication fails

Confirm the Client ID and Secret were issued for the environment matching your **Host** — sandbox credentials don't work against production, and vice versa.

### Retrieval rejected for a missing recipient

With **Direct To Revivn** disabled, the **Return Recipient** address is required in full. Fill in the recipient in the tool's configuration, or enable Direct to Revivn if devices should ship straight to Revivn.

## Related

- [List Revivn Asset Retrievals](https://www.tryrisotto.com/docs/integrations/tools/revivn/list_asset_retrievals) — look up the status or tracking number of an in-flight retrieval

Source: https://www.tryrisotto.com/docs/integrations/tools/revivn/create_asset_retrieval
