Actions20
- Asset Actions
- Creative Actions
- Brand Actions
- Project Actions
- Folder Actions
- Account Actions
Overview
This node integrates with the Frontify platform to manage and automate creative content workflows. Specifically, the Run Creative Job operation allows users to trigger a rendering/export job for a creative template stored in Frontify. This is useful when you want to programmatically generate creative assets (e.g., images or PDFs) based on predefined templates and variable inputs.
Common scenarios include:
- Automating the generation of marketing materials or branded assets in different formats.
- Dynamically customizing creatives by passing variables to templates.
- Exporting creatives in various file formats and scales for use in campaigns or presentations.
For example, a marketing team could use this node to automatically produce multiple versions of a flyer by changing text or images via variables, exporting them as PNGs or PDFs ready for distribution.
Properties
| Name | Meaning |
|---|---|
| Authentication | Means of authenticating with the service; currently supports "Access Token" |
| Template ID | The identifier of the creative template to use as the source for the creative(s). Required. |
| Format | Output format of the exported creative. Options: PNG, JPG, PDF |
| Scale | Scale factor for the output image. Options: @1x, @2x, @3x |
| Variables | Key-value pairs to customize the template variables dynamically during export |
| Export Options | Additional export options as key-value pairs (not detailed in code usage) |
| Additional Options | Extra settings including: - Token (password field) - Domain (defaults to https://example.frontify.com) |
Output
The node outputs JSON data representing the status of the export job initiated on Frontify. The main fields include:
id: The unique identifier of the export job.status: Current status of the job (e.g., pending, completed).
This output can be used to track the progress of the creative export job or to poll for completion and retrieve the final asset.
If binary data output were supported, it would represent the actual exported creative files, but in this implementation, only job metadata is returned.
Dependencies
- Requires an API authentication token credential to access Frontify's GraphQL API.
- Uses Frontify's GraphQL endpoint (default domain is configurable).
- Relies on n8n helper methods for making authenticated HTTP requests and handling binary data if needed.
Troubleshooting
- Invalid Template ID: If the provided template ID does not exist or is incorrect, the node will fail to start the export job. Verify the template ID is correct.
- Authentication Errors: Ensure the access token is valid and has sufficient permissions to run export jobs.
- Network/Domain Issues: If the domain URL is incorrect or unreachable, the request will fail. Confirm the domain setting matches your Frontify instance.
- Variable Formatting: Variables must be provided as key-value pairs. Missing or malformed variables may cause the export to fail or produce unexpected results.
- Job Status Polling: Since the export job runs asynchronously, you may need to use the "status" operation separately to check job completion.
Common error messages typically relate to invalid input parameters or authentication failures. Resolving these involves verifying credentials, template IDs, and input formatting.
Links and References
- Frontify API Documentation (for GraphQL queries and mutations)
- Frontify Creative Templates (overview of templates and variables)
- n8n documentation on Creating Custom Nodes