Integrations
Zapier
Triggers

Zapier Triggers

Triggers are events in Canvelete (opens in a new tab) that can start your Zapier automations. When something happens in your Canvelete account, these triggers can automatically kick off workflows in other apps.

Available Triggers

New Design

Trigger Key: new_design

Fires when a new design is created in your Canvelete account.

When This Triggers

  • A new design is created manually in the editor
  • A design is created via API
  • A design is duplicated from an existing design
  • A template is saved as a new design

Output Fields

FieldTypeDescription
idStringUnique identifier for the design
nameStringName of the design
descriptionStringDesign description (if provided)
thumbnailUrlStringURL to the design thumbnail image
widthNumberDesign width in pixels
heightNumberDesign height in pixels
statusStringDesign status (DRAFT, PUBLISHED)
visibilityStringVisibility setting (PRIVATE, PUBLIC, UNLISTED)
isTemplateBooleanWhether the design is marked as a template
createdAtStringISO timestamp when design was created
updatedAtStringISO timestamp when design was last modified

Example Output

{
  "id": "design_clx1234567890",
  "name": "Social Media Post",
  "description": "Instagram post for product launch",
  "thumbnailUrl": "https://cdn.canvelete.com/thumbnails/design_clx1234567890.png",
  "width": 1080,
  "height": 1080,
  "status": "DRAFT",
  "visibility": "PRIVATE",
  "isTemplate": false,
  "createdAt": "2024-01-15T10:30:00Z",
  "updatedAt": "2024-01-15T10:30:00Z"
}

Common Use Cases

  • Backup Automation: Automatically backup new designs to cloud storage
  • Team Notifications: Send Slack messages when team members create designs
  • Project Management: Create tasks in project management tools for design review
  • Analytics: Track design creation metrics in spreadsheets or databases

New Render Complete

Trigger Key: new_render_complete

Fires when a design or template rendering is completed.

When This Triggers

  • A design is rendered to PNG, JPG, or PDF
  • A template is rendered with dynamic data
  • Batch rendering operations complete
  • API rendering requests finish processing

Output Fields

FieldTypeDescription
idStringUnique identifier for the render job
designIdStringID of the source design (if applicable)
templateIdStringID of the source template (if applicable)
formatStringOutput format (png, jpg, pdf)
widthNumberRendered image width in pixels
heightNumberRendered image height in pixels
qualityNumberQuality setting used (for JPG format)
fileSizeNumberSize of rendered file in bytes
downloadUrlStringTemporary URL to download the rendered file
statusStringRender status (COMPLETED, FAILED)
processingTimeNumberTime taken to render in milliseconds
createdAtStringISO timestamp when render was requested
completedAtStringISO timestamp when render completed

Example Output

{
  "id": "render_clx9876543210",
  "designId": "design_clx1234567890",
  "templateId": null,
  "format": "png",
  "width": 1080,
  "height": 1080,
  "quality": 90,
  "fileSize": 245760,
  "downloadUrl": "https://cdn.canvelete.com/renders/temp/render_clx9876543210.png?expires=1642176000",
  "status": "COMPLETED",
  "processingTime": 1250,
  "createdAt": "2024-01-15T10:35:00Z",
  "completedAt": "2024-01-15T10:35:01Z"
}

Common Use Cases

  • Social Media Posting: Automatically post rendered images to social platforms
  • Email Marketing: Add rendered images to email campaigns
  • File Management: Organize rendered files in cloud storage with proper naming
  • Quality Assurance: Send rendered images for approval workflows
  • Client Delivery: Automatically deliver completed designs to clients

Trigger Configuration

Polling Frequency

Zapier checks for new triggers based on your plan:

  • Free Plan: Every 15 minutes
  • Starter Plan: Every 5 minutes
  • Professional Plan: Every 2 minutes
  • Team Plan: Every 1 minute
  • Company Plan: Every 1 minute

Filtering Triggers

You can add filters to your triggers to only process specific events:

Filter by Design Properties

// Only trigger for designs with specific dimensions
width: 1080 AND height: 1080
 
// Only trigger for public designs
visibility: PUBLIC
 
// Only trigger for templates
isTemplate: true

Filter by Name Patterns

// Only trigger for designs with specific naming
name: Contains "Social Media"
 
// Exclude certain design types
name: Does not contain "Draft"

Historical Data

When you first set up a trigger:

  • New Design: Returns up to 100 most recent designs
  • New Render Complete: Returns up to 50 most recent completed renders

This ensures your Zap has sample data to work with and can process recent items if needed.

Best Practices

Performance Optimization

  1. Use Filters: Apply filters to reduce unnecessary trigger executions
  2. Batch Processing: Consider using webhooks for high-volume scenarios
  3. Error Handling: Implement proper error handling in subsequent Zap steps

Data Management

  1. Store IDs: Always store the design/render ID for future reference
  2. Handle Duplicates: Use unique identifiers to prevent duplicate processing
  3. Cleanup: Implement cleanup workflows for temporary files

Security

  1. Download URLs: Rendered file URLs are temporary and expire after 24 hours
  2. Access Control: Triggers only fire for designs you have access to
  3. Rate Limits: Be mindful of API rate limits in high-volume scenarios

Troubleshooting

Common Issues

Trigger Not Firing

  • Verify your Canvelete account connection is active
  • Check if the design meets your filter criteria
  • Ensure you have proper permissions for the design

Missing Data

  • Some fields may be empty if not set during design creation
  • Thumbnail URLs may take a few seconds to generate
  • Download URLs for renders expire after 24 hours

Performance Issues

  • Consider using webhooks for real-time processing
  • Implement proper error handling and retries
  • Use filters to reduce trigger volume

For more troubleshooting help, see our troubleshooting guide.

Next Steps