n8n ➔ Vectorizer.AI Payload Specification
Technical reference for automating data exchange between Workflow Automation and Image Processing workflows.
💡 How this integration works:
1. n8n triggers an event when workflow.executed occurs.
2. Data is packaged into a standard JSON webhook payload.
3. Payload is delivered into your Vectorizer.AI intake pipeline and mapped to your Image Processing targets.
Authentication & Event Specs
| Parameter | Source (n8n) | Destination (Vectorizer.AI) |
|---|---|---|
| Auth Mechanism | Header Auth / Basic | Basic Auth (API Key) |
| Trigger Event | workflow.executed | Ingest Pipeline |
Sample Webhook JSON Payload
{
"event": "workflow.executed_to_vectorizer",
"timestamp": 1788105197,
"source": {
"platform": "n8n",
"auth_mode": "Header Auth / Basic",
"data": {
"execution_id": "sample_execution_id_val",
"workflow_name": "sample_workflow_name_val",
"node_output": "sample_node_output_val",
"timestamp": "sample_timestamp_val"
}
},
"destination": {
"platform": "Vectorizer.AI",
"auth_mode": "Basic Auth (API Key)",
"target_endpoint": "https://api.vectorizer.com/v1/ingest",
"mapped_fields": {
"task_id": "{{source.execution_id}}",
"output_format": "{{source.workflow_name}}",
"svg_data_url": "{{source.node_output}}",
"processing_ms": "{{source.timestamp}}"
}
}
}
Quick Integration Setup
- Retrieve your secret API credentials from your n8n developer dashboard using authentication method
Header Auth / Basic. - Configure the target endpoint URL to route payloads into the Vectorizer.AI 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 Header Auth / Basic credentials. |
422 Unprocessable | Schema Error | Check field keys alignment between source and target payload. |