How to Use Make.com to Automate Appliance Lookups (No-Code Guide)

Why This Matters

Most CRMs and dispatch platforms — Workiz, Housecall Pro, ServiceTitan, or custom systems — store appliance data but do not enrich it. That means no specs, no diagrams, no recall data, and no model validation.

With a simple Make.com automation, every new job gets automatically enriched with verified appliance data the moment it is created. No developer needed.

What You Are Building

A no-code automation pipeline:

CRM → Make.com → ApplianceAPI → CRM

Make.com is the "glue" connecting your CRM to ApplianceAPI. When a job is created, Make.com automatically calls ApplianceAPI, gets structured appliance data, and pushes it back into your system.

Before automation: CSR creates job, customer gives model number (sometimes wrong), technician shows up underprepared, diagnosis delayed, second trip required.

After automation: Job created in CRM, Make.com triggers instantly, ApplianceAPI returns verified model data, specs, and recall status, technician sees everything before arrival. Fewer callbacks, faster diagnosis, more revenue per tech.

Step 1: Create a Scenario in Make.com

Log into Make.com and click "Create a new scenario." You will see a blank canvas — this is where your automation lives.

Step 2: Add a Trigger

You need something to start the automation when a new job is created.

Option A: Webhook (most flexible). Add a Webhook module, select "Custom Webhook," and copy the generated URL. Your CRM sends job data to this URL whenever a new job is created.

Option B: Native app integration. If your CRM (Workiz, Housecall Pro, etc.) has a native Make.com integration, connect directly and set the trigger to "New Job Created."

Step 3: Add an HTTP Module (Call ApplianceAPI)

This is where the enrichment happens. Click Add Module → HTTP → Make a Request and configure:

• Method: GET
• URL: https://api.applianceapi.com/v1/models/{{model_number}}
• Headers: Authorization: Bearer YOUR_API_KEY

Map the model_number field from your webhook or CRM trigger. ApplianceAPI normalizes messy inputs automatically.

Step 4: Map the Response Data

After the HTTP call, ApplianceAPI returns structured JSON data. Add another module to your scenario (CRM update, Slack notification, Google Sheet, etc.) and map the response fields:

• brand — Verified manufacturer name
• category — Appliance type (refrigerator, washer, etc.)
• image_url — Product photo for reports or tickets
• dimensions — Height, width, depth
• confidence — Data quality score (HIGH, MEDIUM, LOW)
• recall_status — CPSC recall status
• age_estimate — Manufacture year and month

Step 5: Send Data Back to Your CRM

Depending on your CRM, you can update job fields, add structured notes, attach photo links, or create internal alerts. Your CRM becomes data-rich instantly — every job has verified appliance information before the technician leaves the shop.

No-Code Use Cases You Can Build

Once the basic pipeline is set up, you can extend it:

• Auto-enrich every job — Verified model, appliance type, manufacturer, and specs added automatically to new jobs.
• Technician pre-dispatch alerts — Send a Slack or SMS message with appliance details before the tech arrives on site.
• Recall flagging — If a recalled appliance is detected, alert the dispatch team automatically.
• Auto-populate CRM fields — Fill appliance category, brand, and age fields without relying on manual CSR data entry.
• Pre-diagnosis workflows — Suggest likely parts and attach relevant manuals to the job record automatically.

Compatible Platforms

This workflow pattern works with any platform that supports webhooks or API calls:

• Workiz
• Housecall Pro
• ServiceTitan (via V2 API or webhook)
• Custom CRMs and dispatch systems
• Internal tools and spreadsheets
• Zapier (similar workflow, different automation platform)

Make.com acts as your universal connector — if your tool can send or receive HTTP requests, it works.