Manual property lookups don't scale. When your team processes five leads a day, copying property data from external sites into Salesforce is annoying but manageable. When you're processing fifty, it becomes a bottleneck that slows down your entire operation.
The solution is automation. With Datalara installed in your Salesforce org and a simple Flow, every new lead or address change can trigger an automatic property data lookup. The result lands directly on the record — 230+ fields covering valuation, ownership, liens, deeds, MLS data, and more — without anyone lifting a finger.
Here's how to set it up.
Prerequisites
Before building the Flow, make sure you've completed the initial Datalara setup:
- Install the Datalara managed package from AppExchange (takes under a minute)
- Configure the Named Credential with your API password (provided when you register at datalara.com)
- Choose your target object — which Salesforce object will receive property data (Lead, Account, or a custom object)
- Map your fields — select which Datalara fields map to which Salesforce fields on your chosen object
If you haven't done these steps yet, follow the complete setup guide first.
Choosing Your Flow Trigger
Salesforce Flows support several trigger types. The right one depends on your workflow:
Record-Triggered Flow (Most Common)
Fires automatically when a record is created or updated. This is the best option for most teams.
Use cases:
- A new Lead is created with a property address — automatically enrich it
- An address field is updated on an existing record — re-fetch with the new address
- A checkbox field is set to true — trigger an on-demand lookup
Screen Flow (Button Click)
A user clicks a button on the record page to manually trigger a property lookup. Good for teams that want control over when lookups happen (and when credits are consumed).
Scheduled Flow
Runs on a schedule — daily, weekly, or monthly. Useful for re-enriching existing records with fresh data or processing a batch of records that were imported without property data.
Building a Record-Triggered Flow
Here's a step-by-step walkthrough for the most common scenario: automatically looking up property data when a new Lead is created.
Step 1: Create the Flow
In Salesforce Setup, navigate to Flows and click New Flow. Select Record-Triggered Flow.
Step 2: Configure the Trigger
- Object: Lead (or your chosen object)
- Trigger the Flow When: A record is created
- Condition Requirements: Add a condition to ensure the address fields aren't empty. For example:
Street is not null AND City is not null AND State is not null
This prevents the Flow from firing on leads that don't have address data yet.
Step 3: Add the Datalara Action
In the Flow builder, add an Action element. Search for the Datalara invocable action (installed with the managed package). Configure it with:
- Record ID — The ID of the Lead record that triggered the Flow
- Street Address — Map to the Lead's street field
- City — Map to the Lead's city field
- State — Map to the Lead's state field
- ZIP Code — Map to the Lead's ZIP field
Step 4: Save and Activate
Save the Flow and activate it. From this point forward, every new Lead with a valid address will automatically receive a full property data enrichment.
What Happens After the Lookup
Once the Flow triggers a Datalara lookup, the mapped fields are populated on the record within seconds. Depending on which fields you mapped, your team will see:
- Property details on the page layout — valuation, structure info, owner details
- Financial data — LTV, equity, open liens, mortgage balances
- Market data — MLS listing status, days on market, last sale price
- Risk indicators — foreclosure status, distressed sale flags, lien count
Because this data lives on standard Salesforce fields, it's immediately available for:
- Reports — Filter leads by property value, equity percentage, or foreclosure status
- Dashboards — Visualize your pipeline by property characteristics
- List Views — Sort and filter records by any mapped property field
- Additional Flows — Trigger follow-up actions based on property data (e.g., auto-assign high-equity leads to senior brokers)
Flow Design Tips
Guard Your Credits
Each successful property lookup consumes one credit from your monthly allocation. Add conditions to your Flow trigger to avoid unnecessary lookups:
- Only fire when address fields are populated
- Use a checkbox field like "Property Data Fetched" to prevent duplicate lookups on the same record
- Consider using a Screen Flow for manual control if credit conservation is a priority
Handle Updates Thoughtfully
If you want to re-fetch property data when an address changes, create a separate Flow that triggers on record update with the condition: Street field IS CHANGED. This ensures you get fresh data for the new address without re-fetching on every minor record edit.
Batch Processing
For importing a list of addresses and enriching them all, use a Scheduled Flow or a Screen Flow with a record collection. This lets you process records in bulk rather than one at a time.
No Code Required
The entire setup — from package installation to field mapping to Flow creation — is done through Salesforce's point-and-click interface. There's no Apex code to write, no middleware to configure, and no external integration platform to manage. If your team can build a Salesforce Flow, you can automate property data enrichment.
Ready to automate your property lookups? Install Datalara and build your first Flow today.