Actions20
- Asset Actions
- Creative Actions
- Brand Actions
- Project Actions
- Folder Actions
- Account Actions
Overview
This node integrates with the Frontify platform, enabling users to manage digital assets and related resources programmatically. Specifically, the Asset - Update operation allows updating metadata of an existing asset within a specified library. This is useful for enriching assets with custom metadata fields, improving organization, searchability, and contextual information.
Common scenarios include:
- Adding or modifying descriptive metadata on images, documents, or other digital assets.
- Synchronizing asset metadata from external systems into Frontify.
- Automating updates to asset properties as part of larger workflows involving asset lifecycle management.
Example: A marketing team automatically tags product images with campaign-specific metadata after upload, ensuring consistent categorization across projects.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with the service; currently supports "Access Token" only. |
| Asset ID | The unique identifier of the asset to update. |
| Library | The destination library where the asset resides; selected from available libraries. |
| Metadata | Collection of key-value pairs representing metadata fields to add or update on the asset. |
| Additional Options | Optional parameters including: - Token (an API token, if needed) - Domain (Frontify instance URL, defaulting to https://example.frontify.com) |
Output
The output JSON contains the result of the metadata update operation:
- When updating metadata, the node first fetches the library's custom metadata property definitions.
- It then maps provided metadata keys to their corresponding property IDs.
- Finally, it sends a mutation request to add or update the custom metadata on the specified asset.
- The response includes confirmation data such as parent asset IDs indicating successful update.
The output JSON structure typically looks like this (simplified):
{
"metadata": {
"customMetadataProperties": [
{
"id": "property-id",
"name": "Property Name",
"type": { "name": "string" }
}
]
},
"update": {
"parentIds": ["asset-id"]
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Frontify GraphQL API.
- Needs an API authentication token (access token) configured in n8n credentials.
- The node dynamically loads available libraries via a GraphQL query to populate the "Library" dropdown.
- The domain URL for the Frontify instance can be customized via additional options.
Troubleshooting
- Missing or invalid Asset ID: The operation requires a valid asset ID. Ensure the asset exists and the ID is correctly passed.
- Invalid metadata keys: Metadata keys must match existing custom metadata properties in the selected library. If keys do not exist, the update will silently ignore them.
- Authentication errors: Verify that the access token is valid and has sufficient permissions to update assets.
- Network or API errors: Check connectivity to the Frontify instance and confirm the domain URL is correct.
- Empty metadata collection: If no metadata values are provided, the node will only fetch metadata properties without performing an update.
Common error messages may include permission denied, invalid input, or resource not found. Resolving these usually involves verifying credentials, input parameters, and resource existence.