Overview
This node acts as a webhook trigger for Frontify events, specifically listening to asset-related events within a chosen library. It is designed to handle real-time notifications from Frontify when assets are created or updated in a specified library. This is useful for automating workflows that depend on changes in digital asset libraries, such as syncing assets to other systems, triggering approval processes, or updating metadata.
Practical examples include:
- Automatically syncing newly created or updated assets from a Frontify library to a DAM (Digital Asset Management) system.
- Triggering notifications or tasks in project management tools when assets change.
- Updating website content or marketing materials dynamically based on asset updates.
Properties
| Name | Meaning |
|---|---|
| Library | Choose the specific Frontify library to listen to for asset events. Options are loaded dynamically from available libraries associated with the user's account. |
| Events | Select which event(s) to listen for. Currently supports: "Asset Created or Updated". |
Output
The node outputs JSON data representing the webhook payload received from Frontify. The json output field contains the full body of the incoming webhook request, which includes details about the asset event triggered (e.g., asset creation or update). This allows downstream nodes to access all relevant information about the asset event.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential to connect securely to Frontify's GraphQL API.
- Uses Frontify's GraphQL API to:
- Load available libraries for selection.
- Manage webhook registration and deletion.
- Requires the workflow to be accessible via a public URL to receive webhook calls from Frontify.
Troubleshooting
- Webhook URL not reachable: Ensure the n8n instance is publicly accessible or tunneled properly so Frontify can send webhook requests.
- Library selection empty or incorrect: Verify that the API credentials have sufficient permissions to list libraries.
- Webhook creation failure: Check API credentials and network connectivity; ensure the webhook URL is correctly configured and unique.
- No events triggered: Confirm that the selected event type matches the actual events occurring in the Frontify library.
- Error responses from Frontify API: Review API limits, authentication tokens, and query correctness.