Actions20
- Asset Actions
- Creative Actions
- Brand Actions
- Project Actions
- Folder Actions
- Account Actions
Overview
This node enables interaction with the Frontify platform, specifically allowing users to create folders within a Frontify library or folder structure. It is useful for organizing digital assets, projects, or other resources by programmatically creating new folders in a specified location.
Common scenarios include:
- Automatically creating project-specific folders when onboarding new projects.
- Organizing assets into hierarchical folder structures based on metadata or workflow triggers.
- Integrating Frontify folder creation into larger automation workflows that manage digital asset management.
For example, you could use this node to create a new folder named "Marketing Campaign 2024" inside an existing parent folder or library, helping keep your Frontify workspace organized.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with the service. Only option: Access Token |
| Parent Folder or Library ID | The ID of the parent folder or library where the new folder will be created. Optional. |
| Folder Name | The name of the folder to create. Required. |
| Description | A textual description of the folder. Optional. |
| Additional Options | Collection of optional parameters: - Token (API token, password type) - Domain (Frontify domain URL, default: https://example.frontify.com) |
Output
The output JSON contains details of the newly created folder, including:
id: The unique identifier of the created folder.name: The name of the folder.creator: An object with the creator'sidandname.createdAt: Timestamp of folder creation.breadcrumbs: An array representing the folder's path hierarchy, each withidandname.
Example output snippet:
{
"id": "folder123",
"name": "My Folder",
"creator": {
"id": "user456",
"name": "John Doe"
},
"createdAt": "2024-01-01T12:00:00Z",
"breadcrumbs": [
{ "id": "lib789", "name": "Library Name" },
{ "id": "folder101", "name": "Parent Folder" }
]
}
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token (access token) to authenticate requests to Frontify.
- Uses GraphQL API calls to Frontify's endpoint, which defaults to
https://example.frontify.combut can be customized. - The node depends on n8n's HTTP request capabilities and helper methods to perform GraphQL queries and mutations.
Troubleshooting
- Authentication errors: Ensure the provided access token is valid and has sufficient permissions to create folders.
- Invalid parent ID: If the parent folder or library ID is incorrect or does not exist, the mutation will fail. Verify the ID before running.
- Missing required fields: The folder name is mandatory; omitting it will cause an error.
- Network or API errors: Check connectivity to the Frontify domain and ensure the API endpoint is reachable.
- Permission issues: The authenticated user must have rights to create folders in the specified parent location.
If an error occurs, the node will throw an error indicating the issue. Using the "Continue On Fail" option allows processing subsequent items even if one fails.
Links and References
- Frontify API Documentation (for detailed API usage and schema)
- GraphQL Basics (to understand the query and mutation structure used)
- n8n Documentation (for general node usage and error handling)