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

Questions people ask

Which Propera plans include API access?

Pro and Business. The scenario authenticates with an API key from your account, and a Starter key returns a 403 on every call. Confirm the plan before building the scenario rather than after.

Does Make's free tier cover this?

For most lead volumes, yes. A single underwriting call is one HTTP module operation plus whatever your trigger and write-back steps use, so the operation count per lead is small. The binding constraint is usually your Propera monthly ARV allowance rather than Make's operations.

Does each scenario run use one of my monthly ARVs?

Yes. Every completed analysis draws one AI ARV from your plan's monthly allowance. When the allowance is exhausted the API returns 402 and the module errors until the limit resets on your next billing cycle.

How do I avoid underwriting leads that are not ready?

Add a Make filter before the HTTP module. Requiring a non-empty address is the minimum useful filter; a lead-status or tag condition is better. Each run costs an ARV, so filtering is about your allowance rather than only about tidiness.

What does the scenario do when an address fails to match?

The API returns a 422 with a message and no estimate, so the module errors rather than writing an empty or wrong value into your record. Missing street numbers are the usual cause.