Zapier: Push property name (not just property ID)

I am utilizing the new Zapier integration to add guest name and phone number to my Contacts in Open Phone. I'm also able to pull over the dates of stay, and I'd like to add in the property name for where they will be staying. Right now, the data available within Zapier from OR just includes the Property ID, which is just the internal ID number in OwnerRez. Having the internal property name as an available data point would be a huge help and would make multiple Zap prossiblites even more beneficial! Specifically for my Zap usage, this would allow us to see, on quick glance, where and when a guest is staying with us when they reach out via call or text. 

--

For context, my current Zaps: 

Step 1: Create contact in OpenPhone when contact created in OwnerRez

Step 2: Update contact in OpenPhone with dates of stay when booking created in OwnerRez

Hi Alece,

That's a good suggestion and we'll be looking at adding this to the trigger data along with other things such as basic guest details in the next update to the integration.

In the mean time, you can use a Property Lookup action after the trigger to grab the property details using the `property_id` field from the Booking trigger.

In the mean time, you can use a Property Lookup action after the trigger to grab the property details using the `property_id` field from the Booking trigger.

Can you clarify what you mean here, Joel? 

Sure. After the trigger add another step and choose OwnerRez again and scroll down to the "Property Lookup" action. Follow through the prompts, and on the "Set up action" select the Property ID from step 1 like this:

That is a HUGE help! I believe, in the same vein, I could use the Guest Lookup to add all guest contact information to avoid the double-zaps I'm currently needing to get Contact info to merge with Booking info? 

Yep! 

We are intending to expand the triggers to include more info so you can save steps, but for now the Lookups serve as workarounds, as well as if you are querying with data from other systems.

Wonderful! Thank you for letting me know this was possible as a workaround in the meantime. Very helpful!

[Another topic was closed as a duplicate of this topic (https://www.ownerrez.com/forums/requests/zapier-combine-data-available-in-booking-and-contact-triggers)]

Hey Joel -- 

Since I shared my previous Zap links, here's an update. I consolidated things into one Zap (combining those actions as you described them): 

Create contact in OpenPhone with when booking created in OwnerRez »

It's still not 100% correct, as something with the Guest Lookup continues to error out (though it works fine when testing). For some reason, on every new booking, it sends an error that says, "Guest:Id:181738969 not found". Literally the same ID number every single time -- which isn't even correlated to any guest or booking I have. I cannot figure out where it's pulling that number from, and don't know if there's an issue with the Zap trigger or what. (Have you successfully used Guest Lookup on other Zaps??)

Just received this back from Zapier support: "The root cause of this is the fact new data coming in from the OwnerRez trigger is not including the guest ID. I have created a bug report and have passed along this information to OwnerRez."

Hopefully this can be corrected quickly between OR and Zapier so that we can effectively make use of this integration!

Hi Alece,

Yep. Zapier sent us that ticket and I responded to them.

What you are seeing is an Owner Block trigger. In our backend, Bookings and Owner Blocks are the same structure, so both can fire zap triggers (not to mention other things within OwnerRez). We are going to enhance the integration to include an option on the trigger for whether you want it to fire for blocks or no, but in the mean time, add a Zapier Filter action between your Trigger and your Guest Lookup. Tell it to continue only if  "Is Block" is false:

Perhaps the example the Zapier support staff sent was (mistakenly) a block rather than a booking, so I've gone ahead and added the filter as that's a huge help anyway. BUT the Zap does not work and gets hung up on the same error message I sent you in a previous comment here. Same error message on every new booking that comes in. 

Sorry Alece, I hadn't seen your last screenshot.

That error message is indeed coming from OwnerRez, and it means that the Guest ID you are attempting to look up could not be found in OwnerRez. I did a quick check on that ID (181738969) and indeed there is no Guest in your account with that ID. I suspect that some other ID is getting sent to the Guest Lookup action. Can you post a screenshot of the Guest Lookup action in your Zap showing the arguments passed to it?

It's pulling the Guest ID field from Step 1 (Booking created in OwnerRez):

That looks right. I wonder if they are automatically sending some other ID when there is no guest ID in the case of a block. If that is true, than the error should only occur on Blocked Off Time, so adding the filter will eliminate it.

I checked our logs for the past week, and I do see that your Zap is requesting that same non-existent Guest ID quite often. Can you make sure you have published the most recent version of your Zap just to make sure there are no changes left in Draft?

Correct -- I'm currently on version 21 of the Zap (Lord have mercy!) and that's the one that's published and in use. 

In case it helps you dig into it as well, the Zapier support reply did state this as to that number that appears to be a Guest ID in the error I receive:

--

"I can explain the guest ID that you're seeing. Every step in a Zap has a unique ID number. So the number 181738969 is the step ID number of the trigger in your Zap:
 When the trigger comes back empty, there's a placeholder value which is a combination of the step ID and the value it's looking for surrounded by curly brackets. In this case, it would look like {{181738969__guest_id}}. Step 2 of your Zap is taking the step ID and using it in place of the guest ID.
 
The root cause of this is the fact new data coming in from the OwnerRez trigger is not including the guest ID. I have created a bug report and have passed along this information to OwnerRez. Zapier works as quickly as possible to fix bugs once they are identified; however, due to the nature of bugs we are not able to provide an ETA for if and when a solution will be implemented. I have added your email address to the list of impacted users. Once a fix has been implemented, we will send you an email letting you know you can try to use this feature again."

Aha! That makes sense, and explains why I couldn't identify that ID from anywhere. If that's true, than the error should go away with the filter on `is_block`.  

Not sure why it would have been erroring on actual bookings and not just blocks without that filter, but as soon as my next booking comes in... I'll let you know if the Zap works normally or not!