AI guest messaging and upsells for Smoobu
TravelPal connects to Smoobu with an API key and secret you make. It answers guests on the booking's thread and writes paid arrival or departure times to the booking.
One Smoobu connection works in both directions. Each item is explained below.
What TravelPal reads from Smoobu
Smoobu is the system that European hosts and small property management companies use. Their apartments are listed on Airbnb, Booking.com and German-language regional portals. Many also use several iCal feeds.
Apartments become properties
Smoobu keeps an apartment's name in one place and its details in another. TravelPal reads both. The address, the apartment's own time zone and the amenity list arrive together. So do the property type and the currency. Bed counts come across as Smoobu splits them. Double, single, sofa, queen, king and child beds are kept apart. A party of six gets a real answer about how they will sleep, not only a bed total. Smoobu publishes no photo resource, so pictures are the ones you put in your guidebook.
Bookings, and nothing that is only a calendar block
Smoobu stores blocks as bookings, on channels that its own list calls Blocked channel. TravelPal knows them and skips them. No guest link is made for an owner stay or a maintenance hold. What is left is real. Smoobu has no inquiry state and no pending state. Every stay the concierge greets is a guest who is really coming.
The thread is the booking
Smoobu keeps messages on the booking, not in a separate inbox. One stay is one conversation, and there is nothing to match up. The history comes in oldest first. The booking also carries the channel's own reference code. So the concierge can quote the Airbnb or Booking.com number the guest can see. It does not give a Smoobu id.
One guest record across stays
A Smoobu guest keeps the same record from one booking to the next. A second visit is already linked to the first. The returning-guest profile joins on that record. Preferences, past questions and what the guest bought last time are there before they write.
What a night is worth, split into its parts
The total on a Smoobu booking is one number with no currency on it. So TravelPal reads the price elements and takes the accommodation line with its own currency code. Rates and minimum stays come from your Smoobu calendar, for each apartment, in that apartment's currency. That is why an upsell quote is in euros when the unit is in Berlin.
What TravelPal writes back to Smoobu
Every message goes out through Smoobu, never around it. So your Smoobu inbox shows exactly what each guest was told.
Replies on the booking's own thread
TravelPal answers through Smoobu, on the booking the guest wrote from. That booking's message history is the whole record, and there is no second inbox to check. Direct bookings are answered at the address Smoobu holds for that guest. So are bookings from your own Smoobu booking page.
Paid time changes, on the booking
A guest may pay for a late departure or an early arrival. TravelPal writes it to the arrival and departure times on the Smoobu booking. Your cleaners read the real time from the booking they already use. See how upsells work for what is offered and when.
One field at a time
Smoobu's booking update takes only the field that changed, so TravelPal sends the time and nothing else. Your staff may have edited a price, a note or a guest detail five minutes ago. That edit stays exactly as they left it.
Connected in four steps
You create the access details yourself, inside Smoobu. TravelPal does the rest itself.
Generate the key and secret in Smoobu
Go to Settings, then Advanced, then API Keys. The key starts with a prefix such as usr_live_. The secret appears once, when you press Generate Secret, so copy it then. Smoobu cannot show it again, but you can generate a new one whenever you want. You make both halves yourself, and nobody at Smoobu has to say yes first.
Paste both into TravelPal
Both are required. TravelPal checks them against your Smoobu account when you save. From then on, every request is signed with the pair. That is the only method Smoobu accepts after September 25, 2026. You have nothing to do when that date passes. The connection is covered by the flat price. See what it costs.
One address, every Smoobu event
Smoobu sends the account's whole event stream to each address registered on it. There are no choices to make for each event. One registration covers new bookings, changes, cancellations and new guest messages. TravelPal registers its own address. It removes the address again if you disconnect.
Apartments import, then the channel check
Your apartments become properties, and your bookings load with their message history. Your Smoobu account may take Airbnb or Booking.com bookings. If so, someone on your side first sends one real message from that account. They note where the guest received it. After that, TravelPal answers those guests.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the Smoobu connection will not do
Know the limits of Smoobu before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Airbnb and Booking.com guests wait for one check
Smoobu's send call has a message body and nothing that names the channel the message goes out on. Its published reference does not say where a message to an Airbnb or Booking.com guest appears. It could be the channel's own thread, the Smoobu guest app, or email. A message to an Airbnb guest outside the platform can get a host delisted. So TravelPal does not guess. Direct bookings and bookings from your own Smoobu page are answered from the first day. Channel guests are answered after one check. Someone sends one real message on your account and writes down where it arrived. Until then, TravelPal stays quiet with them, rather than quote an upsell it cannot deliver.
No team-only note inside Smoobu
Smoobu's booking notes are single text boxes, and a save overwrites the whole box. Its host message is not documented as hidden from the guest. So there is no line inside Smoobu that only your team can read. TravelPal leaves those boxes alone and never uses a guest-visible message instead. A question it holds for a person goes to your team's channel and inbox. Sale records take the same route. Both stay outside Smoobu.
Extra nights cannot be written onto a Smoobu booking
Smoobu's booking update accepts an arrival time and a departure time, and no dates at all. So an added night has nowhere to go on the booking. TravelPal sells early arrival and late departure here. It sends an extra-night request to your team, with the nights already checked against your Smoobu rates. It does not sell something it cannot record.
The message history carries no clock and no author
A Smoobu message arrives with its text and its direction, inbox or outbox, but no send time. Nothing says who on your side wrote an outbox line. Your own reply and a Smoobu automatic template look the same. TravelPal reads a booking's thread in the order Smoobu numbered it, not by the clock. Smoobu announces a guest's message and says nothing about yours. So the concierge steps back on your written rules and your quiet hours. It cannot see a colleague start to type.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.
Smoobu integration FAQ
Where do I get the Smoobu API key and secret?
In your own Smoobu account, under Settings, then Advanced, then API Keys. The key starts with a prefix such as usr_live_. The secret appears once, when you press Generate Secret. Copy it then, because Smoobu cannot show it again. If you miss it, generate a new secret and paste that one. Nobody at Smoobu has to approve anything first.
Can TravelPal answer my Airbnb and Booking.com guests on Smoobu?
Yes, after one check on your account. Smoobu's send call has no channel selector. Its reference does not say where a message to a channel guest lands. It could be the channel's own thread or email. So one real message goes out on your account first, and where the guest received it is recorded. Direct bookings and bookings from your own Smoobu page are answered from the first day.
What happens to my Smoobu calendar blocks?
Nothing. Smoobu records a block as a booking on a channel named Blocked channel. TravelPal reads that and skips it. No guest link is made and no welcome message goes out. An owner stay or a maintenance hold never shows up as a guest waiting for an answer.
How does a paid late checkout reach my Smoobu booking?
It is written as a departure time on the Smoobu booking. That is where your cleaning schedule already looks, so nothing has to be copied anywhere. TravelPal sends that one field and leaves the rest of the booking alone. Smoobu's update takes no dates, so an added night stays with your team.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Smoobu in how widely they are used.
Updated