​@poypoy This is strange because URL of phone recording is an attribute that appears by default it doesn’t have to be declared before hand. That being said, the only way the URL wouldn’t appear is if a recording of this call didn’t occur or doesn’t exist. Can you verify there is a recording for this call in the UI?

Hi ​@robintrainward, thanks for commenting! Unfortunately, the URL didnt appear by default in testing. That’s why I was confident to use Recordings URL attribute as it is the attribute that appears during testing, however during actual while published, that attribute is not exactly the one I was expecting, it has this URL attribute. When finding new records to test, I couldn’t return real recordings even if there is actually a call being completed.

Hi there, ​@poypoy and ​@robintrainward! 

Hope you don’t mind me jumping in here. It looks like the fields in the test record differ from those that come through when the Zap runs live. So I wanted to suggest selecting a live Zap run for the test record instead—this should let you map the url field that is available during a live run but isn’t in the default test records. 

You can find more details on how to do that here:  Select from previous Zap run.

Can you give it a try and let us know how it goes?

Hello ​@SamB, thank you so much for this huge help! I didn’t know we can set zap runs as trigger sample. Thank you! 

You’re welcome ​@poypoy! I’m so pleased that did the trick. 

Hope you have a great rest of your week, happy Zapping!