Actions22
- Asset Actions
- Autofill Actions
- Brand Template Actions
- Comment Actions
- Design Actions
- Design Import Actions
- Export Actions
- Folder Actions
- Resize Actions
- Key Actions
Overview
This node integrates with the Canva API to manage digital assets such as images, videos, and audio files. Specifically, the Asset - List operation retrieves a list of assets associated with the user’s Canva account. This is useful for workflows that need to fetch and process media assets stored in Canva, for example, to automate content curation, backup, or further processing in other tools.
Practical examples include:
- Automatically listing recent images or videos from Canva to use in social media posts.
- Fetching assets to generate reports or galleries.
- Paginating through large asset collections for batch processing.
Properties
| Name | Meaning |
|---|---|
| Limit | Maximum number of items to return. Accepts values between 1 and 100 (default varies: 10 or 50). |
| Continuation | Token used for pagination to continue fetching results from where the last request ended. |
Note: The node input properties for this operation allow controlling how many assets are retrieved per request and support pagination via continuation tokens.
Output
The node outputs a JSON array of asset objects representing the user's Canva assets. Each asset object typically includes metadata such as asset ID, name, type (image, video, audio), tags, and other relevant details provided by the Canva API.
If the node supports binary data output (not explicitly shown here), it would represent the actual media files of the assets; however, based on the static code, the output focuses on JSON metadata about assets.
Dependencies
- Requires an API authentication token credential for Canva's OAuth2-based API.
- The node makes HTTP requests to
https://api.canva.com/rest/v1/assetsendpoint. - Proper configuration of the API key/credential in n8n is necessary for successful communication.
Troubleshooting
Common issues:
- Invalid or expired API token leading to authorization errors.
- Exceeding the maximum allowed limit or invalid limit values causing request failures.
- Incorrect continuation token resulting in empty or error responses during pagination.
Error messages and resolutions:
- 401 Unauthorized: Check that the API authentication token is valid and has not expired.
- 400 Bad Request: Verify that the 'limit' parameter is within the allowed range (1-100) and the continuation token is correct.
- Empty response or no assets returned: Confirm that the user account has assets and that any filters or parameters are correctly set.