Trouble with Zap sending wrong Property Radar records to Docupost and missing PDF URL.

  • 15 September 2023
  • 5 replies

I can’t get this Zap to work. The Zap tests show they are integrated. The zap is suppose to take new property records from Property Radar and send them to Docupost so a letter gets sent out. When I test the Docupost integration, it always pulls up a property record from Property Radar that is not in the list that I added to the Zap. The test does send a record to Docupost, but it is the wrong property record and the PDF doesn’t show even though I added a PDF URL.

5 replies

Userlevel 7
Badge +14

Hi @NDOshogun 

Good question.

Please post detailed screenshots with how your Zap steps are configured to help us have context.

If you watch this video, you will see the Zap is looking like it is working. The record that gets pulled up is a record that is not in the list attached to this Zap and the PDF letter never shows in Docupost.

Userlevel 7
Badge +14


There was no sound on the video.


When testing PR, it may be pulling back sample records.


The Sq Ft variable at the end may be breaking the static URL.


Try turning the Zap ON and testing.

Then check your Zap Runs history log details to see the DATA IN/OUT for each Zap step.

I removed the square foot error on the PDF URL. Zap history shows no history for Task Usage or Zap Runs.

It still is not working.

Userlevel 7
Badge +14


Zaps work while turned ON for new data going forward.

Have there been new records added to the list in PR since the Zap was turned ON?

If you are still having issues with the Zap trigger, then try reaching out to PropertyRadar.

PR likely created and manages their Zap app integration.

You may need to adjust your PR settings and or plan to get this working correctly.