Hi @Alba SH 

Make sure to test your Hostaway Zap trigger step to pull thru data.

You can also try turning the Zap ON and testing live.

Then check your Zap Runs history details to see the DATA IN/OUT for each step to trace and troubleshoot: https://zapier.com/app/history/

Help article from Hostaway: https://support.hostaway.com/hc/en-us/articles/1260801753750-Zapier-Hostaway-App

I have the same issue - no listing names are pulling through. Would love to know if it’s a bug. I also am not getting triggers for reservation updates - only new bookings

@Alba SH and @avin22 

If you suspect an issue, you can try these options:

• Contact Hostaway Support for help troubleshooting their Zap app integration
• Open a ticket with Zapier Support: https://zapier.com/app/get-help

Hi avin22,

After test the Zap it’s working good. So I guess it showing “no data” but in real condition it’s working great.

Yay! Glad to hear it’s working @Alba SH!

If it’s sending over the listing name correctly when the Zap runs live then it could be that there’s a bug with how the test records are loaded from Hostaway. Would you mind reaching out to the Support team here to flag this? They’ll be able to dig into the logs to confirm if this is a bug can open up a bug report if necessary.
 

@avin22 - are you able to see the listing name as well when the Zap runs live for new bookings?

And with it not triggering for updated bookings can you share some further details as to what type edits are being made to the bookings that are failing to trigger the Zap? And @Alba SH can you confirm whether it’s triggering for updates to existing as well as new bookings?

For example is the same type of update being carried out - a change to the length of the stay or an update to the guest email address etc.? If it’s the same type of update it’s failing to trigger on would you be able to make some different types of updates to the booking information to see if it’s able to trigger on those edits? This will help to narrow down whether it’s all updates that it’s failing to trigger on or just certain types of updates it’s missing.

Looking forward to hearing from you both!

@SamB I did some further testing and it appears the zap only triggers when the reservation first moves from “new” to “modified” status. If you make a modification to a previously modified booking, it does not trigger the zap

Thanks for letting me know @avin22. That’s very strange, the New / Updated Reservation trigger should be triggering whenever a booking is updated regardless of whether it has previously been modified. So to me this behaviour seems to likely be caused by a bug.

Please use the form here to let our Support team know that this is happening. They can then check the logs for the Zap to see if we’re being sent any data for the subsequent updates, even though it’s not triggering, and open up a bug report so that the developers of the Hostaway app can investigate further. 

Please do keep us updated on how you get on with them, I’m keen to ensure this gets sorted!