Vectorizer.AI ➔ Make.com Payload Specification
Technical reference for automating data exchange between Image Processing and Automation workflows.
💡 How this integration works:
1. Vectorizer.AI triggers an event when vectorization.completed occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your Make.com intake pipeline and mapped to your Automation targets.
Authentication & Event Specs
| Parameter | Source (Vectorizer.AI) | Destination (Make.com) |
|---|---|---|
| Auth Mechanism | Basic Auth (API Key) | API Key Header |
| Trigger Event | vectorization.completed | Ingest Pipeline |
Sample Webhook JSON Payload
{
"event": "vectorization.completed_to_make",
"timestamp": 1788105197,
"source": {
"platform": "Vectorizer.AI",
"auth_mode": "Basic Auth (API Key)",
"data": {
"task_id": "sample_task_id_val",
"output_format": "sample_output_format_val",
"svg_data_url": "sample_svg_data_url_val",
"processing_ms": "sample_processing_ms_val"
}
},
"destination": {
"platform": "Make.com",
"auth_mode": "API Key Header",
"target_endpoint": "https://api.make.com/v1/ingest",
"mapped_fields": {
"execution_id": "{{source.task_id}}",
"scenario_id": "{{source.output_format}}",
"status": "{{source.svg_data_url}}",
"data_output": "{{source.processing_ms}}"
}
}
}
Quick Integration Setup
- Retrieve your secret API credentials from your Vectorizer.AI developer dashboard using authentication method
Basic Auth (API Key). - Configure the target endpoint URL to route payloads into the Make.com intake pipeline.
- Map incoming schema properties according to the JSON specification detailed above.
Expected HTTP Response Codes
| Status Code | Meaning | Troubleshooting Step |
|---|---|---|
200 OK | Success | Payload accepted and queued for routing. |
401 Unauthorized | Auth Failure | Verify headers for valid Basic Auth (API Key) credentials. |
422 Unprocessable | Schema Error | Check field keys alignment between source and target payload. |