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 create an import job that imports a design from a publicly accessible URL. It is useful when you want to bring external design files into Canva for further editing or use within your workflows. For example, you might have a design file hosted on a public server or cloud storage and want to automate its import into Canva without manual upload.
The "Create URL Import Job" operation initiates this import process by sending the URL of the design file to Canva's import endpoint. Optionally, you can specify a title for the imported design.
Properties
| Name | Meaning |
|---|---|
| Import URL | The public URL of the file to be imported into Canva. This must be accessible without authentication. |
| Import Title | Optional title to assign to the imported design once the import completes. |
Output
The node outputs JSON data representing the response from the Canva API after creating the import job. This typically includes details about the import job such as its ID, status, and metadata related to the imported design.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token (OAuth2) configured in n8n credentials to authorize requests to the Canva API.
- The node sends HTTP POST requests to
https://api.canva.com/rest/v1/importsendpoint. - The provided import URL must be publicly accessible for Canva to fetch the design file.
Troubleshooting
Common issues:
- Providing a non-public or inaccessible URL will cause the import to fail because Canva cannot retrieve the file.
- Missing or invalid API authentication token will result in authorization errors.
- Incorrectly formatted URLs or unsupported file types may cause the import job creation to fail.
Error messages:
- Authorization errors usually indicate problems with the API token; ensure the credential is valid and has required scopes.
- 400 Bad Request errors may indicate missing required parameters or invalid URL format.
- 404 Not Found or similar errors may occur if the import job ID is incorrect when checking status (not applicable here but relevant for follow-up operations).