HappyFox - Create/Update Asset

HappyFox - Create/Update Asset creates or updates assets in HappyFox with data from Axonius.

Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note


Required Fields

These fields must be configured to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Action to perform - Select whether to create a new asset or update an existing asset in HappyFox.

    • Create Asset - Creates a new asset in HappyFox
    • Update Asset - Updates an existing asset in HappyFox
  • Asset Type ID - The ID of the asset type in HappyFox where the asset should be created or updated. To find asset type IDs, use the HappyFox API endpoint /api/1.1/json/asset_types/.

  • Agent ID - The ID of the HappyFox agent who is creating or updating the asset. The agent must have the Manage Assets permission. To find agent IDs, refer to the HappyFox staff list in your account.

  • Use stored credentials from adapter - Select this option to use credentials from the HappyFox adapter connection. By default, the first connection is selected.

    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

📘

Note:

Using stored credentials from the adapter requires that the adapter is configured successfully with at least one connection.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

📘

Note:

For details, see Axonius to External Field Mapping.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  • HappyFox Domain - The full URL of your HappyFox instance. Example: https://yourcompany.happyfox.com. If you are using a custom domain, use the custom domain URL.

  • API Key - The API Key generated from your HappyFox account.

  • Auth Code - The Auth Code generated from your HappyFox account.

  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the HappyFox Asset Management API - POST /api/1.1/json/assets/

Required Ports

Axonius must be able to communicate via the following ports:

  • TCP port 443 (HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

  • Manage Assets - Required for the agent to create and update assets in HappyFox
  • Manage all Contacts - Required if the agent needs to create contacts when creating or updating an asset
  • The agent specified in the Agent ID field must be an active agent with the appropriate permissions

Authentication Method:

API Key and Auth Code authentication using HTTP Basic Authentication format. The API Key is used as the username and the Auth Code is used as the password.

Note: The exact permission names should be confirmed with your HappyFox administrator or HappyFox support, as the API documentation is not publicly available.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
API 1.1YesHappyFox Asset Management API