Syncing Agoda and Traveloka calendars so a room never sells twice

HostBooking · Updated Nov 2, 2026 · 7 min read

Agoda can import an outside calendar by iCal under Calendar connections, but only for single-room types and without saying how often it re-reads. Traveloka publishes no iCal guide for TERA. This is the least automated pair: use booking emails from both, let Agoda read a central calendar, close Traveloka by hand, and keep a daily close-out routine.

Why this pair is harder

With Airbnb or Booking.com you know how often a calendar is re-read (3 hours, 2 hours). With Agoda and Traveloka, neither gives a number: Agoda has iCal but no published interval, and for Traveloka we found no official documentation on iCal in TERA at all. You cannot just link and forget. You need a routine.

Putting three pieces together

1. Emails from both OTAs into one calendar. Forward Agoda and Traveloka confirmations to HostBooking. Each properly signed email becomes a booking with guest name, dates and price. Emails usually arrive as soon as the guest books, faster than any calendar read.
2. Agoda reads your central calendar. Paste HostBooking’s link into Agoda’s Calendar connections. A Traveloka booking (arriving by email) then blocks Agoda on Agoda’s next read.
3. Traveloka by hand. For each Agoda booking, close the nights in TERA. Without a channel manager there is no automatic route.

Since Agoda’s delay is unknown, measure it once: block a far-off night on your HostBooking calendar, note the time, and see how long Agoda takes to close it. Use that as a minimum to judge which bookings also need closing by hand on Agoda.

A daily close-out routine

When neither OTA updates quickly on its own, a fixed habit helps more than any setting:

Setting it up

1. On Agoda, split multi-room types into single-room types if you want iCal. Agoda may switch off the connection of a type changed from 1 room to several.
2. In HostBooking, Calendar → Sync OTAs (iCal): paste each Agoda type’s Copy calendar link and set the channel to Agoda.
3. Copy HostBooking’s link for Agoda and paste it into Other website link in Calendar connections, name it, click Import.
4. Under Booking emails from OTAs, create the address and set a filter forwarding Agoda and Traveloka emails to it.
5. Measure Agoda’s delay as above and write it down.
6. Agree the close-out times and the "close in TERA" step with whoever is on duty.

What does not cross over

• Prices and promotions: each OTA runs its own deals; nothing travels by iCal or email to the other.
• Rooms left: iCal is busy/free only, which is why Agoda requires single-room types.
• TERA receives nothing automatically without a channel manager.

When a channel manager makes sense

If you have several identical rooms, or both OTAs bring plenty of bookings, a channel manager connected to Agoda and Traveloka is the practical answer: it sends rooms left to both, with no manual closing. When you switch, remove the old iCal connection on Agoda so two sources are not editing the same calendar.

If a double booking still happens

Agoda: if another room is free, move the guest to an equal or better one at no extra cost. If none is free, you must find accommodation of equal or higher standard elsewhere and provide transport there.

Traveloka: we found no public partner rule. Contact your Traveloka account contact at once and offer the guest comparable accommodation.

Because Agoda’s rule is explicit and puts the cost on you, work out the cost of relocating an Agoda guest before deciding which booking to keep. Either way, tell the guest as early as you can.

On HostBooking

OTA calendar sync reads Agoda’s calendar every 5 minutes, reads Agoda and Traveloka booking emails, and warns you when a night is double-booked. HostBooking does not update TERA for you. See booking email forwarding, the background iCal sync guide and the pricing page.