Integrating PropertyRadar with REI Pulse Webhook
Integrating PropertyRadar with REI Pulse Webhook
Objective
This video explains how to connect PropertyRadar to REI Pulse so new matched records are automatically pushed into the CRM for AI-driven follow-up. It also covers how to verify the integration with a test lead and confirm the record appears correctly in REI Pulse.
Key Steps
1. Confirm prerequisites in PropertyRadar 0:22
Verify you have access to a PropertyRadar account.
Create or select the list you want to automate.
Make sure the list is configured with the filters you want so it continuously looks for new matching records.
2. Enable automations on the PropertyRadar list 0:30
Turn on Automations for the selected list.
Confirm the list is set to monitor for new matching records on an ongoing basis.
Understand that when a new record matches the list filters, it will be added automatically to the list.
3. Open the prebuilt PropertyRadar workflow in REI Pulse 1:25
In REI Pulse, go to Automation.
Open Client Workflows.
Locate the LeadGen folder.
Find the prebuilt workflow labeled PropertyRadar.
Use this workflow as the base for the integration instead of building one from scratch.
4. Add an inbound webhook trigger 2:03
In the PropertyRadar workflow, add a new trigger.
Select Inbound Webhook as the trigger type.
Copy the generated webhook URL because it is unique to your account/workflow.
Keep this copied webhook ready for the PropertyRadar setup.
5. Add the webhook inside PropertyRadar 2:37
Go back to PropertyRadar.
Open Settings or Account Settings.
Scroll to Integrations.
Add a new integration and choose Webhook.
Label or connect it to REI Pulse.
Paste the webhook URL copied from REI Pulse into the webhook field.
6. Send a test record from PropertyRadar 3:06
In PropertyRadar, click Add webhook if needed.
Use Send Test Record to push sample data to REI Pulse.
This sends the full payload, including available property details such as:
Property information
Beds
Baths
Rooms
Other available record fields
7. Fetch the sample request in REI Pulse 3:41
Return to the REI Pulse webhook trigger.
Click Fetch Sample Requests.
Select the test record that was just sent from PropertyRadar.
Review the incoming fields to confirm the payload was received correctly.
Save the trigger after the sample data loads.
8. Remove the unnecessary auto-created contact step 4:06
After saving the trigger, REI Pulse may automatically add a Create a Contact step.
Delete the extra step with the warning icon if it appears.
Do not keep duplicate contact creation steps, since the workflow already handles contact creation later.
9. Verify workflow mapping and save the action 4:40
Open the Create a Contact step and confirm the fields are already mapped.
Check that there are no errors in the mapped fields.
Confirm tags and webhook payload data are populated correctly.
Review the Phone and Create Opportunity steps.
If needed, change the destination from the default AI seller prospector to another pipeline or team.
Save the action and then Publish the workflow.
10. Enable the PropertyRadar list automation settings 5:46
Return to the PropertyRadar list.
Make sure Enable Automations is turned on.
Set the automation to trigger on New Matches.
Avoid using Status Changes if you want to prevent duplicate sends.
Optionally enable a Daily Summary if desired.
11. Configure append options and integration routing 6:13
Purchase and enable phone append so records include phone numbers.
If needed, enable email append as well.
In the Integrations section, select the REI Pulse integration you created.
Confirm the list is now connected to the correct CRM workflow.
12. Choose mobile-only filtering if needed 6:49
If your process requires it, filter to mobile numbers only.
If a number is not recognized as a cell phone, the record can still be routed for manual calling.
Decide whether to include emails based on your outreach process and data needs.
13. Understand skip tracing costs and record limits 7:22
Review your PropertyRadar plan to understand how many records are included.
Know that additional skip-traced records may cost $0.08 per record.
Remember that skip tracing charges are billed through PropertyRadar, not REI Pulse.
14. Repeat the setup for additional lists 7:50
If you have more than one list, repeat the same automation and integration setup.
For each list, confirm:
Automations are enabled
New matches are selected
The correct REI Pulse integration is chosen
Append options are enabled as needed
15. Push a live test lead from the list 8:23
Go into the PropertyRadar records area.
Select a record or push the entire list if needed.
Choose Export to Integration.
Continue through the prompts.
Confirm whether you want phone append and email append.
Approve the prompts to send the lead into REI Pulse.
16. Confirm the lead arrived in REI Pulse 9:07
Open the REI Pulse workflow and check Enrollment History.
Verify the test lead appears in the workflow.
Go to Opportunities and confirm the record is present in the correct pipeline.
Check that the contact name and property address match the test record.
17. Verify mapped data and begin outreach 9:48
Review the notes and mapped fields in the contact record.
Confirm available data such as:
Contact name
Email
Primary phone number
Property details
If the phone number is available, begin the communication process or let the AI workflow handle outreach automatically.
Cautionary Notes
Do not keep duplicate contact-creation steps in the REI Pulse workflow; delete the extra auto-generated step if it appears.
Avoid using Status Changes in the PropertyRadar automation if you want to prevent duplicate record pushes.
Make sure the webhook URL is pasted correctly; a wrong or incomplete URL will break the integration.
Phone append is required if your process depends on calling leads.
Skip tracing costs are billed by PropertyRadar, so review your plan before sending large volumes.
If a number is not identified as mobile, it may route to manual calling rather than automated texting.
Tips for Efficiency
Start with the prebuilt PropertyRadar workflow in REI Pulse to save setup time.
Use a test record first before pushing full lists.
Keep the integration focused on New Matches to reduce duplicate records.
If your team only works mobile numbers, enable mobile-only filtering early.
Repeat the same setup pattern for each list to keep your process consistent.
After publishing, do a quick check of Enrollment History and Opportunities to confirm the workflow is working end-to-end.