Virima Connector

🔌 Virima Connector

This connector enables seamless integration with the Virima platform to fetch hardware inventory and blueprint data.

⚡ Actions

Fetch Devices

Retrieves all devices from Virima with pagination support. It automatically filters out archived devices and CI parts to ensure data quality.

📥 Input Parameters

• page_size (Integer, optional): Number of devices per page, from 1 to 1000 (Default: 100).

📤 Output

• total: The total number of devices found in Virima.

• has_next_page: A boolean indicating if additional pages of data are available.

• devices: An array of device objects including:
  • id and record_id: Unique identifiers.
  • blueprint: Information regarding the device type, icon, and component.
  • properties: Custom device properties including property names and values.
  • last_modified_on: Timestamp used for tracking changes.

📌 Use Cases

• CMDB Synchronization: Keeping Xurrent Configuration Items up to date with Virima data.

• Asset Tracking: Discovering and mapping hardware assets across the organization.

• Product Cataloging: Creating product categories based on device blueprints.

⚠️ Notes

• Prerequisites: Requires a Virima API Key with CMDB read permissions and a valid Tenant ID.

• Filtering: Unlike some other connectors, Virima does not support server-side filtering by modification time; pagination is handled automatically using offset-based state.

• Authentication: Uses custom header-based authentication (Api-Key and Tenant-Id).

‍