Actions20
- Asset Actions
- Creative Actions
- Brand Actions
- Project Actions
- Folder Actions
- Account Actions
Overview
This node integrates with the Frontify platform to manage digital assets within libraries. Specifically, the Asset - Search operation allows users to find assets in a chosen library by specifying search criteria such as keywords, tags, and metadata filters. This is useful for quickly locating relevant assets in large collections, enabling efficient asset management workflows.
Common scenarios include:
- Searching for images or documents tagged with specific keywords.
- Filtering assets based on custom metadata fields defined in a library.
- Using either simple keyword searches or complex custom queries to refine results.
Example use case: A marketing team wants to find all assets related to "mountain" that are tagged with "summer" and have a metadata field "Location" set to "Alps". They can configure this node to perform that search and retrieve matching assets automatically.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with Frontify. Only "Access Token" option is available, requiring an API token credential. |
| Library | Selects the target library where the asset search will be performed. The list is dynamically loaded from available libraries in the connected Frontify account. |
| Custom query | Boolean toggle to choose between writing a custom JSON query or using the simplified search interface. |
| Query | When "Custom query" is enabled, this JSON input allows specifying a raw query object to filter assets. |
| Search | When "Custom query" is disabled, this string is a simple keyword search term to find assets (e.g., "mountain", "people"). |
| Tags | When "Custom query" is disabled, this JSON array of strings filters assets by tags. Assets must match at least one tag (logical OR). Example: ["first tag", "second"]. |
| Metadata | When "Custom query" is disabled, this fixed collection allows specifying multiple metadata key-value pairs. All specified metadata fields must match (logical AND). Each entry has a "Name" (metadata key) and "Value". |
| Additional Options | Optional extra settings including: • Token: An optional token string (password type). • Domain: The Frontify domain URL, defaulting to https://example.frontify.com. |
Output
The output is a JSON array of asset objects matching the search criteria. Each asset object contains at least:
id: Unique identifier of the asset.title: Title or name of the asset.
The node returns up to 100 matching assets per execution.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential to connect to Frontify.
- Uses Frontify's GraphQL API endpoint, configurable via the "Domain" property.
- The node dynamically loads available libraries from the connected Frontify account to populate the "Library" dropdown.
Troubleshooting
- Empty results: If no assets are returned, verify that the selected library contains assets matching your search criteria. Check spelling and case sensitivity in tags and metadata keys/values.
- Invalid JSON in Query or Tags: When entering JSON manually (for "Query" or "Tags"), ensure it is valid JSON syntax. Malformed JSON will cause errors.
- Metadata filtering not working: Confirm that the metadata keys used exist in the selected library. The node fetches custom metadata properties dynamically; if keys do not match exactly, filters will fail.
- Authentication errors: Ensure the provided API token is valid and has sufficient permissions to access the library and assets.
- API domain misconfiguration: If you changed the "Domain" property, verify the URL is correct and accessible.
Common error messages may include:
- Authorization failures due to invalid or missing token.
- GraphQL errors indicating malformed queries or unknown fields.
- Network errors if the domain is unreachable.
Resolving these typically involves checking credentials, verifying input formats, and confirming network connectivity.