Atera

What You'll Need

• Access to retrieve Atera API credentials.
• Admin or super-admin user role within Hudu.

Integration Features

• Companies
  • Create client spaces within Hudu directly from Atera companies, or seamlessly merge them into existing (already-created) client spaces.
• Contacts
  • Pull contacts directly from Atera and easily sort them into an asset layout of your choice ("People", "Contacts", "Company A employees", etc.)
• Devices
  • Pull device information from Atera; sorted into asset layouts based on set sort rules and your default sync locations.

What Hudu needs from Atera

• API Key.

Obtaining the Atera Information

• Navigate to the Atera dashboard >> Admin.
• Click on API.
• Copy the API key.

Enabling the Atera Integration

• Integrations can be enabled at any time, during Hudu environment testing or in production.

• Once enabled, integrations can be merged into existing documentation based on predefined rules.

• This allows you to configure the integration upfront or connect it later as needed.

• To enable the Atera integration:

  • Navigate to the Hudu admin area (Admin → Integrations).

  • Select Atera from the list.

Setting up the Integration in Hudu

Step 1. Connect to Atera

• Enter API Key

• Select Default Asset Layouts

  • Choose asset layouts (must be active asset layouts) from the list to designate as the default asset layouts

  • They store information that is pulled in but not explicitly mapped to another asset layout

• The Atera integration requires three default asset layouts for:

  • Contacts
  • Devices
  • SNMP Devices

• Select any additional options:
  • Auto-update names of Assets - If name is changed in Atera, the name will automatically be updated in Hudu
  • Do not update basic company details - This will prevent the company details from being changed in Hudu if they are changed in Atera
  • Match assets on primary serial - This option tells Atera to match devices using their primary serial number. It helps ensure that assets are correctly identified and reduces the chance of duplicates when device names or other attributes change.

Step 2. Test connection and run an initial sync

• On the integration overview page, click Test Connection
• If successful, start an initial sync to bring in Atera companies

Step 3. Match Companies

• Before companies from Atera can be brought into Hudu, they must be matched to:

  • Existing companies in Hudu, or

  • New companies you create in Hudu

• Hudu recommends matching one client first for testing to ensure data imports correctly

• When the integration runs successfully for the first time:

  • Companies from Atera are imported

  • They appear in the Matched Companies List for the integration

• Navigate to Hudu Admin → Integrations → Atera

• Open the integration and click Match Companies

• Review the list of companies and choose one of the following options:

  • Bulk create and/or match all companies

  • Match a company to an existing Hudu company

  • Create a new matched company in Hudu from a Atera company

  • Leave a company unmatched (it and its data will not be imported)

• After matching companies, re-run the integration import to populate data for the matched or newly created companies
   

Step 4. Choose where data will fill

• Add Sort Rules for Devices and SNMP Devices

  • Sort Rules determine how data types from Atera are mapped to asset layouts in Hudu

  • They let you define specific rules that control where each asset type is placed

  • Any asset types imported without an assigned Sort Rule will automatically be placed into the default asset layout

  • Asset layouts used for Sort Rules can be created ahead of time in the Hudu admin area (Admin → Asset Layouts) and must be marked as Active

  • You can also create new asset layouts directly from this section if needed.

FAQ