Make (Integromat) Integration

Build powerful visual workflows with Make's intuitive interface.

Setup

1. Create new scenario in Make
2. Add trigger module
3. Add HTTP → Make a request module
4. Configure request

Configuration

Method

POST

URL

https://api.canvelete.com/api/v1/render

Headers

Authorization: Bearer cvt_YOUR_API_KEY
Content-Type: application/json

Body Type

Raw (application/json)

Body

{
  "designId": "YOUR_DESIGN_ID",
  "format": "png",
  "quality": 90,
  "dynamicElements": {
    "title": "{{1.title}}",
    "image_url": "{{1.image}}"
  }
}

Example: Airtable → Image

1. Trigger: Watch records (Airtable)
2. HTTP Request: POST to Canvelete
3. Map fields:
   • {{1.Name}} → dynamicElements.headline.text
   • {{1.Attachments[].url}} → dynamicElements.photo.src

Variable Mapping

Map Make module data to Canvelete:

Data Structures

Make automatically parses JSON responses. Access fields:

{{3.data.imageUrl}}
{{3.data.width}}
{{3.data.height}}

Common Workflows

Scheduled Report → Chart

Trigger: Schedule (daily 9am)
Action: Fetch data, generate chart image

Webhook → Social Media

Trigger: Webhook trigger
Action: Generate image, post to Twitter/LinkedIn

Database → Email Campaign

Trigger: PostgreSQL watch rows
Action: Generate personalized images for email

Error Handling

Use Make's error handling:

1. Error Handler Route – Add alternative path for errors
2. Ignore Module – Skip errors and continue
3. Rollback – Undo previous operations on failure
4. Break – Stop scenario execution

Advanced Features

Iterators

Process arrays of data:

Iterator → HTTP Request (for each item)

Aggregators

Combine multiple results:

HTTP Requests → Aggregator → Single output

Data Stores

Cache results between runs:

Check Data Store → If missing → Generate Image → Store

Accessing Image URL

After successful render:

{{body.data.imageUrl}}

Use in subsequent modules (email, storage, social post).

Rate Limits

Make executes modules sequentially. For high-volume scenarios:

• Use Sleep module to throttle requests
• Enable caching with "cache": true
• Use Repeater with delays

Troubleshooting

Connection Timeout

• Increase timeout in HTTP module settings
• Use webhook for long-running renders

Invalid JSON

• Verify JSON syntax in body
• Use Make's JSON validator
• Check for proper string escaping

Missing Fields

• Use Get function to safely access nested data
• Add Router for conditional logic
• Validate data before HTTP request

Best Practices

1. Test each module individually
2. Use filters to prevent unnecessary calls
3. Enable scheduling during off-peak hours
4. Set up monitoring with error notifications
5. Use data stores to avoid duplicate renders
6. Add retry logic for transient failures

Pricing Considerations

Make charges per operation. Optimize by:

• Filtering data early in scenario
• Batching requests when possible
• Caching frequently used images
• Using webhooks instead of polling