Connect Your CRM to Propera with Make.com

Overview

Make (formerly Integromat) calls Propera's HTTP API with its built-in HTTP module, so there's no app to install on Propera's side. A free Make account supports multi-step scenarios and routers, so you can branch on success vs. failure without paying.

What you'll build

One scenario: CRM trigger → HTTP "Make a request" (Propera) → Router → CRM update (one route for success, one for failure).

Before you start

• A Propera account on the Pro or Business plan, and a Propera API key (Step 1).
• A Make account (the free tier works for moderate volume).
• Your CRM connected to Make.

Step 1 — Generate your Propera API key

In Propera, go to Account Settings → API Keys, click Generate API Key, name it (for example Make), and copy it. It's shown only once.

Step 2 — Add a trigger from your CRM

Start a new scenario and add your CRM as the first module (watch new/updated records), or a "Custom webhook" the CRM posts to. Use a deliberate "ready" signal (a status field set to Run ARV, or a filter that requires the key fields) so it doesn't run on half-entered leads.

Step 3 — Add the HTTP "Make a request" module

• URL: https://getpropera.com/api/v1/arv
• Method: POST
• Headers: X-API-Key = your key, and Content-Type = application/json
• Body type: Raw, content type JSON, with the lead's fields mapped in:

{
  "address": "{{ lead address }}",
  "property_type": "sfh",
  "bedrooms": {{ beds }},
  "bathrooms": {{ baths }},
  "sqft": {{ sqft }},
  "year_built": {{ year }},
  "comp_radius": 5
}

Turn on Parse response so Propera's JSON fields become mappable in later modules.

(See Make's help docs for the HTTP module.)

Step 4 — Route the result back to your CRM

Add a Router after the HTTP module:

• Route A (filter success = true): your CRM "Update a record", mapping arv, summary_text, and run_url.
• Route B (filter success = false): your CRM "Update a record", writing error into a notes/error field.

Request fields

Response fields

Troubleshooting