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 various Frontify resources such as assets, projects, brands, folders, accounts, and creatives. Specifically, for the Folder - Delete operation, it allows users to delete a folder by specifying its unique folder ID.
Common scenarios where this node is beneficial include automating the cleanup of unused or obsolete folders in Frontify libraries, managing folder structures programmatically, or integrating folder deletion into larger workflows that maintain digital asset organization.
For example, a marketing team could use this node to automatically remove temporary project folders after campaign completion, ensuring their Frontify environment stays organized without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with Frontify; currently supports "Access Token" authentication. |
| Folder ID | The unique identifier of the folder to be deleted. This property is required for deletion. |
| Additional Options | Optional settings including: • Token: An API token (password type) • Domain: The Frontify domain URL, defaulting to https://example.frontify.com |
Output
The output JSON contains the result of the folder deletion mutation. Specifically, it returns an object with an ids field listing the IDs of the deleted folders (in this case, typically a single folder ID).
Example output structure:
{
"ids": ["folder-id-deleted"]
}
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Frontify GraphQL API.
- Needs an API authentication token (access token) configured in n8n credentials.
- Optionally, the user can specify a custom Frontify domain URL if not using the default.
Troubleshooting
Common Issues:
- Invalid or missing Folder ID: The node requires a valid folder ID to delete; ensure the ID exists and is correct.
- Authentication errors: Ensure the provided access token is valid and has sufficient permissions to delete folders.
- Network or domain misconfiguration: Verify the domain URL is correct and accessible.
Error Messages:
- Errors related to authorization usually indicate invalid or expired tokens; refresh or update the token.
- Errors about folder not found suggest the folder ID does not exist or the user lacks permission.
- GraphQL errors may occur if the API schema changes or if required parameters are missing.
Resolving these typically involves verifying input parameters, checking API credentials, and confirming network connectivity.
Links and References
- Frontify API Documentation (for detailed API usage and GraphQL schema)
- n8n Documentation (for general guidance on using credentials and nodes)