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 for the Asset resource with the Tag operation, it allows adding tags to an existing asset in Frontify. This is useful for organizing and categorizing assets by keywords or labels, improving searchability and management within Frontify libraries.
Common scenarios include:
- Automatically tagging newly uploaded assets based on metadata or external data.
- Bulk updating asset tags to reflect changes in project requirements or classifications.
- Enhancing asset discoverability by applying consistent tagging conventions.
Example: Adding tags like ["marketing", "Q2 campaign"] to an asset identified by its ID to group it with other marketing materials for the second quarter campaign.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with the service. Only option available: Access Token |
| Asset ID | The unique identifier of the asset to which tags will be added. Required for this operation |
| Tags | JSON array of strings representing the tags to add to the asset. Example: ["tag1","tag2"] |
| Additional Options | Optional collection including: - Token (API token as password input) - Domain (Frontify domain URL, default: https://example.frontify.com) |
Output
The output JSON contains the updated asset information after tags are added. It includes:
id: The asset's unique identifier.tags: An array of tag objects, each with:value: The tag string.source: The origin/source of the tag.
This confirms which tags are currently associated with the asset post-operation.
No binary data output is involved in this operation.
Dependencies
- Requires a valid API authentication token (access token) for Frontify.
- Needs network access to the specified Frontify domain (default
https://example.frontify.com). - Uses GraphQL API calls to interact with Frontify services.
- n8n credentials must be configured with appropriate API key/token for authentication.
Troubleshooting
- Invalid Asset ID: If the provided asset ID does not exist or is incorrect, the API call will fail. Verify the asset ID is correct and accessible.
- Authentication Errors: Missing or invalid API token will cause authentication failures. Ensure the token is valid and has sufficient permissions.
- Malformed Tags JSON: The
Tagsproperty expects a JSON array of strings. Invalid JSON or non-string elements may cause errors. Validate JSON format before execution. - Network Issues: Connectivity problems to the Frontify domain can cause request failures. Check network settings and domain correctness.
- Permission Denied: The authenticated user must have permission to modify the asset's tags. Lack of permissions will result in errors.
Error messages typically come from the GraphQL API response and should be inspected for details. Enabling "Continue On Fail" in n8n can help process multiple items even if some fail.