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
The "Get Asset Layouts" operation retrieves a list of asset layouts from the connected service. This node is useful when you want to fetch metadata or configuration details about how assets are structured or displayed within a system. Common scenarios include synchronizing asset layout information for reporting, auditing, or further processing in workflows that manage digital assets.
For example, you might use this node to:
- Retrieve all asset layouts updated within a specific date range.
- Filter asset layouts by name or URL slug to find particular configurations.
- Paginate through large sets of asset layouts to process them in batches.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional filters and pagination controls to refine the results: • Name: Filter asset layouts by their exact name. • Page: Specify which page of results to retrieve (for paginated responses). • Slug: Filter asset layouts by their URL slug. • Updated At: Filter asset layouts based on update timestamps. Supports exact datetime or ranges in ISO 8601 format. |
Output
The node outputs JSON data representing the retrieved asset layouts. Each item in the output typically contains details such as the asset layout's name, slug, update timestamp, and other relevant metadata as provided by the API.
If the API supports binary data related to asset layouts (e.g., layout files or images), the node would include this in the binary output field; however, based on the provided code and properties, the primary output is JSON-formatted metadata.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to access the external service.
- The base URL for the API must be set in the node's credential configuration.
- The node depends on the external service's REST API endpoint that provides asset layout data.
Troubleshooting
- Empty Results: If no asset layouts are returned, verify that your query parameters (name, slug, updated_at) are correct and match existing data.
- Invalid Date Format: When using the "Updated At" filter, ensure dates are in valid ISO 8601 format. Incorrect formatting may cause the API to reject the request or return errors.
- Authentication Errors: Ensure that the API key or authentication token is correctly configured and has sufficient permissions to read asset layouts.
- Pagination Issues: If expecting multiple pages of results, confirm that the "Page" parameter is incremented properly to retrieve subsequent pages.
Links and References
- Refer to the external service’s official API documentation for detailed information on asset layout endpoints and query parameters.
- ISO 8601 date format specification: https://en.wikipedia.org/wiki/ISO_8601