Overview
This node acts as a webhook trigger for real-time notifications from Canva. It listens to various Canva events such as design publication, sharing, updates, comments, exports, folder access requests, suggestions, and user mentions. When an event occurs in Canva that matches the configured event type and optional filters, the node triggers the workflow with detailed event data.
Common scenarios include:
- Automating follow-up actions when a design is published or updated.
- Tracking comments or suggestions on designs for team collaboration.
- Monitoring export completions or failures to manage downstream processing.
- Responding to folder sharing or access requests.
- Notifying users or systems when they are mentioned in Canva.
Practical example: Automatically send a Slack message or email notification whenever a new comment is created on a specific design by filtering on the design ID and event type.
Properties
| Name | Meaning |
|---|---|
| Event | The Canva event that will trigger the webhook. Options: Design Published, Design Shared, Design Updated, Comment Created, Comment Resolved, Export Completed, Export Failed, Folder Access Requested, Folder Shared, Suggestion Created, User Mentioned. |
| Design ID Filter | Optional filter to only trigger the webhook for a specific design ID. Only applicable for design-related events like publish, share, update, comment create/resolve, export complete/failed. |
| Folder ID Filter | Optional filter to only trigger the webhook for a specific folder ID. Applicable for folder access requested and folder shared events. |
| User ID Filter | Optional filter to only trigger the webhook for a specific user ID. Applicable for user mention, comment create, and suggestion create events. |
| Validate Signature | Boolean flag to enable or disable HMAC signature validation of incoming webhook requests for security. Default is true. |
| Webhook Secret | Shared secret used to validate the HMAC signature of the webhook payload. Required if signature validation is enabled. |
Output
The node outputs a JSON object containing the following fields:
event_type: The type of Canva event received (e.g., "design.publish").event_id: Unique identifier of the event.timestamp: Timestamp of the event occurrence.created_at: Creation time of the event.data: The full event payload data from Canva, including details about the design, comment, folder, user, etc.metadata: Additional metadata including:webhook_url: The URL where the webhook was received.processed_at: ISO timestamp when the event was processed.filters_applied: Object showing which filters were applied (event type, design ID, folder ID, user ID).
If the webhook request fails signature validation or does not match the configured event or filters, no output is produced and the webhook response is suppressed.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with Canva's API (configured in n8n credentials).
- Uses a shared webhook secret for HMAC signature validation to ensure security.
- Requires the node to be exposed via a publicly accessible webhook URL to receive Canva events.
Troubleshooting
- Webhook rejected: Assinatura ausente — This error means the incoming webhook request did not contain the required HMAC signature header. Ensure Canva is configured to send the signature and the webhook secret is set correctly in the node.
- Webhook rejeitado: Assinatura inválida — Indicates the HMAC signature validation failed. Verify that the webhook secret matches exactly between Canva and the node configuration.
- If the node does not trigger despite events occurring, check that the selected event type matches the incoming event and that any ID filters (design, folder, user) are correct.
- Make sure the webhook URL is publicly accessible and properly registered in Canva's webhook settings.
- Disable signature validation temporarily to isolate issues related to signature mismatches.