Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation allows you to create (post) a new Asset Layout in the target system. Asset Layouts define how asset information is visually structured and displayed, including which fields, icons, colors, and additional details are included. This is useful for customizing asset management views to fit specific organizational needs or preferences.
Common scenarios include:
- Defining a new layout template for assets with custom fields.
- Setting visual identifiers like icon and color to quickly recognize asset types.
- Configuring whether sensitive data such as passwords or photos should be included in the layout.
- Tailoring asset layouts to different teams or projects by specifying which comments, files, or password types to show.
Practical example: A company wants to create an asset layout named "Server Rack" with a blue background, a server icon, and includes passwords and photos but excludes comments. This node operation can post that configuration to the system.
Properties
Name | Meaning |
---|---|
Additional Body Fields | Optional fields to customize the Asset Layout: |
- Name | Name of the Asset Layout |
- Icon | Icon class name representing the layout |
- Color | Hex code for the background color of the layout |
- Icon Color | Hex code for the icon color |
- Include Passwords | Boolean flag to include passwords in the layout |
- Include Photos | Boolean flag to include photos in the layout |
- Include Comments | Boolean flag to include comments in the layout |
- Include Files | Boolean flag to include files in the layout |
- Password Types | String listing password types, separated by new line characters |
- Fields | JSON array defining the fields included in the Asset Layout |
Output
The node outputs JSON data representing the created Asset Layout object as returned by the API. This typically includes all properties of the newly created layout such as its ID, name, icon, colors, included fields, and other metadata.
If the node supports binary data output, it would relate to any file or photo attachments included in the layout, but this operation primarily deals with JSON data describing the layout configuration.
Dependencies
- Requires an API key or authentication token credential configured in n8n to authorize requests to the target system's API.
- The base URL for the API must be set in the node credentials.
- The node depends on the external API endpoint that accepts POST requests to create Asset Layouts.
Troubleshooting
- Authentication errors: Ensure the API key or authentication token is valid and has permissions to create Asset Layouts.
- Validation errors: If required fields like "Name" are missing or invalid, the API may reject the request. Verify all mandatory fields are correctly filled.
- JSON parsing errors: The "Fields" property expects a valid JSON array string; malformed JSON will cause errors.
- Network issues: Check connectivity to the API base URL and ensure no firewall or proxy blocks the request.
- Unexpected API responses: Review the API documentation for correct field formats and constraints.
Links and References
- Refer to the target system’s API documentation for Asset Layout creation endpoints and field definitions.
- n8n documentation on creating custom nodes and handling JSON input/output.