AI guest messaging for WuBook, Zak and WooDoo
TravelPal connects to WuBook with the Permanent Token and the JSON API key you generate yourself in the Wired dashboard, then answers guests in the Airbnb thread WuBook keeps for their reservation. It reads your rooms, your reservations, your availability, and the language the booking was made in, and it sells late checkout and extra services at your prices. Zak, WooDoo and WuBook are three names for one product on one account, so whichever of them is on your login, this is the page for you.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from WuBook
WuBook is Italy-first and European, run by independent hotels and small apartment portfolios that sell rooms by type rather than whole units, with the vendor putting its own base at more than 22,000 properties.
Rooms become properties
One call brings back every room on the property id you connect, up to the 80 rooms WuBook allows on one property, each with its pictures, its occupancy, and the adults and children it sleeps. Virtual rooms come across too: WuBook lets you sell one physical room under a second configuration, a reservation can land on either, and leaving them out would strand a real stay with no property to attach it to. A WuBook room holds capacity, pictures and rates and very little else, so the address, the rules and the local detail come from your knowledge base.
Reservations arrive as a pointer, and TravelPal reads the booking
WuBook's push says which reservation moved and nothing else, and it sends the same thing whether that booking is new, changed or deleted. So TravelPal goes and fetches the reservation every time and works from the record rather than the notice: the room, the dates, the party size, the total, and the currency it was sold in.
Statuses are numbers, and a change is a new booking
WuBook grades a reservation from 1 to 6. Confirmed and accepted mean the guest is coming and get a concierge, a booking waiting for approval waits until it is confirmed, and refused and the two cancellation grades are never greeted. There is no modified grade at all, because WuBook handles an amendment as a cancellation plus a fresh reservation, so a moved stay arrives as a new number rather than an edit to the old one. When a booking is canceled, WuBook also names who did it, the guest, somebody working in your BackOffice, or the distribution channel, and your team gets that reason in WuBook's own words.
The language and the money the booking was made in
WuBook puts an ISO language code on the customer record of the booking, so the first reply to a German guest is in German, read off the reservation rather than guessed from what they typed. It also carries a three letter currency, which TravelPal reads instead of assuming: on a base this European, treating a euro stay as dollars would misprice every upgrade by the exchange rate.
Availability by the count, and what TravelPal ignores in it
WuBook sells rooms of a type, so a night is a number of units left rather than a yes or a no, and TravelPal reads it that way before offering anybody an extra night. The same response carries prices and restrictions, and WuBook's documentation says those are the standard defaults rather than the plan actually in force, so TravelPal ignores them and prices from your rules. Reads stop at WuBook's published two year horizon.
What TravelPal writes back
Every message goes out through WuBook, never around it, so your own inbox shows exactly what each guest was told.
Replies in the Airbnb thread
WuBook carries one guest messaging rail and it is the Airbnb thread on the reservation. TravelPal answers there, through WuBook rather than around it, so the conversation your team opens in WooDoo is the whole conversation. Nothing goes out by email or SMS, because WuBook has no send for either.
Sales confirmed to the guest, and handed to your team
A late checkout, an early arrival or an extra service is offered and confirmed in the Airbnb thread at your prices, and because nothing can be written onto a WuBook booking that already exists, the sale reaches your team with the stay, the time and the amount attached. The money is yours: TravelPal takes no commission on what it sells. See how the upsells work.
Your rates and your availability are left alone
TravelPal never writes a price or an availability number into WuBook. The availability call sets an absolute count of sellable units rather than placing a hold, so undoing one would mean writing back a number read earlier, and a booking that landed in between would be re-opened by that undo. It is a surface TravelPal does not touch.
Connected in four steps
The credentials are yours to create inside WuBook. TravelPal does the rest itself.
Make the two keys in the Wired dashboard
wubook.net/wauth/wauth/dash/wired/ gives you both: the Permanent Token, which does not expire and has no daily budget, and the wr_ JSON API key. There are two because WuBook runs two APIs under one account, and the token will not authenticate the key's half. No partner form and no approval queue: both are yours to make right now.
Copy the property id
The integer under Hotel ID in the WuBook Account panel. One WuBook account can hold several properties, and each one is its own connection here, with its own rooms and its own reservations.
Name your Airbnb channel, then paste the messaging callback
Open wubook.net/woodoo/channels/, take the id of the Airbnb connection that has message handling switched on, and enter it. TravelPal turns on the reservation push for you. The messaging callback is the one thing WuBook has no method for, so you paste our URL onto the API key in the Wired dashboard by hand, once.
Fill in what a WuBook room does not hold
WuBook stores a room's capacity, pictures and rates, and not its address, its check-in and check-out times, its house rules or its time zone. Those are entered once during onboarding, and the concierge has them from the first message. The time zone is the one to settle first, because WuBook carries none at all and every scheduled message is timed off it.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the WuBook connection will not do
Every property management system draws its own lines, and the ones WuBook draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Airbnb is the only rail WuBook can message on
WuBook's guest messaging covers the Airbnb connection. Booking.com, Expedia, Vrbo and your direct bookings still arrive as reservations and TravelPal reads all of them, but there is no route to those guests inside WuBook, so TravelPal stays quiet on them rather than quoting an upgrade it cannot deliver. If most of your nights come from Booking.com, weigh that before you connect.
Message history older than a week comes back blank
WuBook's own documentation says messages older than a week appear blank and should be saved in advance. So the backfill on the day you connect reaches about seven days rather than a year of conversations, and what sat in those threads before that cannot be recovered from WuBook by anyone. Everything from the day you connect forward is kept, which is a reason to connect ahead of your season rather than in the middle of it.
Nothing edits a reservation that already exists
WuBook can create a booking, confirm one and cancel one, and has no call that changes the dates or the times on a live one. It is the same product decision as the missing modified grade: an amendment on WuBook is a cancellation plus a fresh reservation. A booking there also carries an arrival hour and no departure hour at all. So a paid late checkout is confirmed to the guest and sent to your team with the stay and the new time, rather than moved on the WuBook record for the cleaner to read off.
The thread labels a message guest or property, and nothing finer
Every message WuBook hands back is labeled guest or property, and property is a side rather than a sender: a reply typed by your team in WooDoo, WuBook's own automation, and TravelPal all wear it. Two things follow from that. TravelPal treats nothing on the property side as a fact worth learning, which keeps your team's own words out of your knowledge base, and since the label can never tell it a colleague has stepped in, the handover to a person runs on your rules and your quiet hours. The single write in WuBook's whole messaging surface is a send into that Airbnb thread, so there is nowhere to leave a note meant only for your team: held questions and sale notes reach your team channel and your email instead.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
WuBook integration FAQ
Is Zak the same thing as WuBook?
Yes, and so is WooDoo. Zak is the property management side, WooDoo is the channel manager, and WuBook is the account they both sit on. One set of credentials from that account covers all three, so whichever of the names is on your login, this is the connection you want. If your account holds more than one property id, each id connects on its own.
Can TravelPal answer my Booking.com guests through WuBook?
No. Guest messaging on WuBook runs through the Airbnb connection, and the API has no email or SMS send, so a Booking.com, Expedia or direct guest cannot be reached from inside WuBook. Those reservations still arrive, your team still works them, and TravelPal does not greet or quote a guest it has no way to answer.
Do I need WuBook's permission to connect TravelPal?
No. You generate the Permanent Token and the JSON API key yourself at wubook.net/wauth/wauth/dash/wired/, and you take the Airbnb channel id from wubook.net/woodoo/channels/. There is no partner application. One step is manual on WuBook's side, because there is no method for it: you paste our messaging callback URL onto the API key in that same dashboard, once.
Will TravelPal change my reservations, rates or availability in WuBook?
No. WuBook has no call that edits an existing booking's dates or times, and its availability call sets an absolute count of sellable units rather than placing a hold, so TravelPal writes to neither. What a guest buys is confirmed in the thread and handed to your team with the stay, the time and the amount.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest WuBook in how widely they are used.
Updated