Let Oomnitza be your single source of truth!
You'll get complete visibility of your assets as data from Retriever is automatically transformed into consumable information and actionable insights.
Connect Oomnitza and Retriever in minutes
Follow the steps below to connect Oomnitza and Retriever to use the Retriever submit order preset. You can use this preset to submit a request to an offboarding employee to return a device, all you need to do is give the address where you want the packaged returned. The offboarding employee will receive email notifications once their box is dispatched, and the company will also be kept informed of the status of the return. Currently only laptop return orders may be created with this API.
Navigation
Setting the Retriever subdomain as a global variable
Creating workflows with the API block
Before you start
Best practice
For the integration with Oomnitza, create a dedicated user account.
Authentication is performed using an API key, which can be obtained by any admin in the Retriever portal. When making an API call, the key should be provided in the Authorization header as follows:
Authorization: Bearer <API_KEY>
For further information consult the Retriever: Authentication.
Setting the Retriever subdomain as a global variable
To save time entering information when you create the user integration and the workflow, you can add the Retriever subdomain as a global variable in Oomnitza.
- In Oomnitza, click Settings > Global Settings.
- Click Add new variable (+).
- Enter Retriever.Subdomain as the variable name.
- Enter your Retriever subdomain. If your subdomain is
https://mycompany.helloretriever.com
your subdomain would be:mycompany.
- Save your changes.
Adding the credentials
To stream Retriever user data into Oomnitza, complete the following steps:
- In Oomnitza, click Settings > Credentials.
- Click Add new credential (+).
- Add the information details.
- Click the AUTHORIZATION tab.
- Ensure that API Key is selected as the authorization type.
- Enter Authorization as the name of the token.
- Enter Bearer followed by the API Key. For example,
Bearer abcde-adw3n-jknadd78l1kjndc
. - Ensure that Add to Header is selected.
- Save your changes.
Next
You use the credentials that you added to create and customize your Retriever integrations with Oomnitza.
Creating workflows
Creating workflows with the API block
To reduce your workload and automate complex and repetitive tasks, you can create a workflow with the API block. To create a user workflow, complete the following steps:
- From the menu, you can select People > Workflow.
- Click Add (+). The Begin and End blocks are automatically added to the sandbox.
- Enter the name and a description of the workflow.
- Edit the Begin block by adding the rules that will trigger the workflow. For example, for this preset you may want to create a rule that identifies offboarding employees (such as those with Status=Offboarding).
- Click the Blocks tab, and drag and drop the API block onto the canvas.
- Click the Edit icon.
- Enter Retriever in the Select Preset search field and select the Submit Order preset.
- Click the right arrow > to select your preset.
- Populate the required information in the Configure section. Refer to the Retriever Submit Order preset for further information.
- Connect the blocks.
- Validate, launch, and save your workflow.
The Retriever Submit Order preset
The Submit Order preset creates a device return order. When you select this preset, you need to provide the following:
Authentication and domain details
- Credentials: Your correct Retriever Credentials that you created in Adding the credentials.
- Subdomain. Your subdomain should be derived from the global variable you created when Setting the Retriever subdomain as a global variable. Alternatively, click Set Manually to manually enter your subdomain.
Company return information
- Return Recipient Name
- Return Address Company
- Return Address Line 1
- Return Address Line 2
- Return Address City
- Return Address State
- Return Address Zip
- Display Name
- Notification Email
Response mapping information
Enter the Oomnitza fields you will use to store the JSON values returned in the response:
- Map Retriever ID to Field: The
id
returned in the JSON response. - Map Retriever Box Track to Field: The
outbound_tracking
number returned in the JSON response. - Map Retriever Box Return Track to Field: The
return_tracking
number returned in the JSON response.
You can use the Advanced Mode to configure the message payload. To do this, complete the following steps:
- In the API block window, click the Advanced Mode button located in the upper right of the window.
- Select the Body tab. The offboarding employee info is mapped to custom Oomnitza fields. These fields need to exist in Oomnitza and be populated with user information for this preset to work. Alternatively, if you wish to test the workflow, you can manually enter the employee information.
"employee_info":{ "email":"{{email}}", "name":"{{full_name}}", "address_line_1":"{{home_street}}", "address_line_2":"{{home_line_2}}", "address_city":"{{home_city}}", "address_state":"{{home_state}}", "address_zip":"{{home_zip_plus_4}}" },
- Select the Response tab.
- For troubleshooting purposes, you can map the Response field {{response}} to a custom long text Oomnitza field. Once you have the entire response, you can then map more JSON response values to custom Oomnitza fields. To create a custom field, go to People>Customization in Oomnitza. For further information, see Creating Custom Fields in Oomnitza.
For further information, refer to the Retriever REST API documentation: Submit Order.
For further information on workflows see: Understanding workflows
Workflow block overvie
Unleash the power of Oomnitza
To get valuable actionable insights that help you manage your assets, learn how to:
- Configure dashboards for your users and software
- Configure custom reports about your users and software
- Create workflows to automate tasks
See Getting started for more information.
Comments
0 comments
Please sign in to leave a comment.