Hudu Integration: Frequently Asked Questions
The questions below cover the most common situations with the Hudu integration.
Why aren't a customer's devices showing in Rev.io?
The most common reason is that the customer's company link hasn't been accepted on the Data Sync & Mapping page. Also check that the devices are in a layout you selected, that the layout has a Rev.io asset type, that the devices aren't archived in Hudu, and, if you use a Sync Tag, that the customer has the tag.
Will the integration create duplicates of devices I already have in Rev.io?
The integration is designed to prevent duplicates. A matching serial number or MAC address links the Hudu asset to your existing Rev.io asset automatically, and a close name match is suggested for your review instead of creating a new asset. Filling in Primary Serial in Hudu and mapping MAC Address give the best results.
I edited a synced asset in Rev.io and my change was replaced. Why?
When the Asset Conflict Policy is set to Hudu is the source of truth, Hudu values are applied on each run. Make the change in Hudu and it will display in Rev.io. If your team maintains asset details in Rev.io, change the policy. See the Hudu Integration: Asset Sync article for more information.
I changed a customer's name in Rev.io or Hudu and the other system didn't change. Why?
When the Account Info Conflict Policy is set to Don't overwrite, names and addresses aren't copied between linked records. Choose a source of truth, or Most recent change wins, if you want them to follow each other. Website and parent company sync under every policy.
Why was a new customer created with a TBD address?
The Hudu company didn't have an address, so the Default Customer Address was used. Once the Hudu company has a full address with street, city, state, and ZIP, the TBD address is replaced automatically on both the service and billing address.
I turned on Auto-Create Rev.io Customers, but companies waiting for review weren't created. Why?
The setting only applies to companies the integration finds after you turn it on. Companies already waiting on the Data Sync & Mapping page stay there, so create or link them from that page.
Two of my companies have very similar names. Which customer will they match?
When a name closely matches more than one customer, the integration doesn't guess. It queues the company on the Data Sync & Mapping page so you can choose.
Does the integration create companies or assets in Hudu?
No. New companies and assets are only created in Rev.io from Hudu. In Hudu, the integration only changes company details your Account Info Conflict Policy allows, a linked company's website and parent, the Id in Integration field on companies, and asset fields your Asset Conflict Policy allows.
A password I added in Hudu isn't showing in Rev.io. Why?
Make sure the password is attached to an asset in Hudu, not only to the company, and that the asset is linked to a Rev.io asset. New passwords display after the next scheduled run.
Are passwords stored in Rev.io?
No. Passwords are never saved in Rev.io, in the integration, or in any log. Only each credential's name is stored. The password is read live from Hudu each time someone reveals it.
Reveal doesn't work for anyone. What should I check?
Make sure the Hudu API key used by the integration allows password access. If it doesn't, create a new key that does and update the Hudu connection.
Does the integration sync Hudu articles, procedures, websites, networks, or contacts?
No. It covers companies, assets in the layouts you select, and the passwords attached to those assets.
Can I run the sync more often than hourly?
You can, but it isn't recommended. Hudu limits how often any tool can call it, and that limit is shared with your other Hudu integrations.
What happens if we remove the integration?
Syncing stops and the links between Hudu and Rev.io are deactivated. Linked assets are no longer marked as managed by Hudu, so your team can edit them in Rev.io again. Your customers and assets in Rev.io, and everything in Hudu, are kept. Nothing is deleted.
For more information about the Hudu integration, see the following articles.