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 projects, assets, brands, folders, creatives, and accounts. Specifically, for the Project - Create operation, it allows creating a new project within a specified brand in Frontify.
Typical use cases include automating the creation of projects tied to specific brands, which is useful in digital asset management workflows, marketing campaign setups, or collaborative creative environments where projects need to be programmatically generated based on external triggers or batch processes.
For example, a marketing team could automatically create a new project in Frontify whenever a new campaign is launched in their CRM system, ensuring all related assets and collaborators are organized from the start.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with Frontify; currently supports "Access Token" authentication. |
| Brand ID | The unique identifier of the brand to associate the new project with. |
| Project Name | The name to assign to the newly created project. |
| Additional Options | Optional parameters including: • Token (an additional token, password type) • Domain (Frontify domain URL, default: https://example.frontify.com) |
Output
The output JSON contains the details of the newly created project, specifically:
id: The unique identifier of the created project.name: The name of the created project.
This output can be used downstream in workflows to reference the project for further operations like asset uploads, folder creation, or permission assignments.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Frontify GraphQL API.
- The node uses the Frontify GraphQL endpoint, which by default targets a domain that can be customized via the "Domain" property.
- No other external services or environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Authentication Errors: If the API key or access token is invalid or missing, the node will fail to authenticate. Ensure the correct token is provided and has sufficient permissions.
- Invalid Brand ID: Providing a non-existent or incorrect brand ID will cause the mutation to fail. Verify the brand ID exists in your Frontify account.
- Missing Required Fields: Both "Brand ID" and "Project Name" are required. Omitting these will result in validation errors.
- Network Issues: Connectivity problems to the Frontify domain may cause request failures. Confirm network access and correct domain configuration.
- API Rate Limits: Excessive requests might trigger rate limiting by Frontify. Implement retry logic or reduce request frequency if needed.
Error messages typically come from the GraphQL API response and should be inspected for details. Using the node's "Continue On Fail" option can help handle errors gracefully in bulk operations.
Links and References
- Frontify Official Website
- Frontify API Documentation (for detailed GraphQL schema and mutations)
- n8n Documentation (for general usage of custom nodes and credentials)