n8n, Make, Zapier integration
In brief
The most common adoption path: HTTP Request node to api.askmarcel.app/v1/diagnostic. Ideal for automating support workflows.
Prerequisites
- n8n, Make or Zapier account
- AskMarcel API key (ak_live_)
- Starter tier minimum for production
n8n
- 1
Add HTTP Request node
Method POST, URL api.askmarcel.app/v1/diagnostic.
- 2
Headers
Authorization: Bearer {{$env.ASKMARCEL_API_KEY}} and Content-Type: application/json.
- 3
JSON body
Map brand, model, error_code from your trigger (Zendesk ticket, form, etc.).
Body{ "brand": "{{ $json.brand }}", "model": "{{ $json.model }}", "error_code": "{{ $json.error_code }}" } - 4
Parse response
steps[] → list for email/Slack. source.manual + source.page → citable reference.
Make (Integromat)
- 1
HTTP > Make a request module
POST https://api.askmarcel.app/v1/diagnostic with Bearer token.
- 2
Map fields
Use JSON > Create JSON for body. Parse steps and source in following modules.
Zapier
- 1
Webhooks by Zapier → POST
Diagnostic URL, Authorization Bearer header, JSON payload with brand/model/error_code.
- 2
Formatter
Extract steps and source to feed Gmail, Slack or your CRM.
Outbound webhooks (optional)
For event-driven architecture, configure an AskMarcel webhook (Starter+) that notifies your endpoint when a diagnostic completes.
Verify it works
Run the workflow with a known error code (e.g. Mitsubishi E7). Response must contain non-empty steps[] and source.page.
curl -s https://api.askmarcel.app/v1/diagnostic \
-H "Authorization: Bearer ak_live_..." \
-H "Content-Type: application/json" \
-d '{"brand":"Mitsubishi","model":"Ecodan PUHZ-W85","error_code":"E7"}'Known limitations
- Rate limit: respect your tier quotas
- ManyChat and other conversational bots: prefer Make/n8n as intermediary if JSON mapping is complex
Video coming soon
Notify me