Chula Sync

My dashboard Sign in Home

Support topics

Account, Gmail, and data controls

On your dashboard you can turn off forwarding, clear the saved Gmail app password, and disconnect Gmail send OAuth. You can also revoke Chula Sync in Google Account permissions. To delete your Chula Sync account and tenant data, email [email protected] from your account email. We will verify the request before deletion.

Set up the dedicated Hosting inbox

Inbox OAuth stays off. You need a Google app password for that inbox:

  1. Sign in as the Hosting Gmail that receives Airbnb mail.
  2. Google Account → Security → turn on 2-Step Verification.
  3. App passwords → create one named Chula Sync and paste it on your dashboard.
  4. Point Airbnb Hosting notifications at that same Gmail.

Workspace admins may need to permit app passwords. Open the steps on your dashboard.

Double-book alert

Possible resort booking overlapping an Airbnb stay (Self Marketed nights are excluded). Open View what happened for a short note of what we saw, why it may have happened, and what to do (it can be wrong — do not rely on it). Open Dated trail for the dated steps. We do not store whether Chula replied. Check Chula and Airbnb, fix the conflict yourself, then Mark resolved on your dashboard (/me#double-bookings) or the listing page. The bot does not cancel guests or write Self Marketed.

Stale import

Near-term Chula blocks missing from Airbnb export after the stale-hours threshold. Confirm Airbnb IMPORT URL, wait for lag (hours), re-check export. Long 1BR default-closed ranges may intentionally not alert.

Forward failure

Gmail→Chula MIME did not send. Common causes: missing RFC822, Hosting inbox auth (app password), send OAuth / Owner From mismatch, unmapped listing title, or EMAIL_DRY_RUN=true. Re-save the app password or reconnect Gmail for Chula sends as indicated. Ask your operator to run Test forward (always dry-run). No text stub is sent to Chula on MIME failure.

Paused listing / missing calendar

Operator pause hides the ICS feed (HTTP 404). Remove or pause Airbnb IMPORT before long pauses so Airbnb does not treat a missing URL as an empty calendar. Emergency sync guards keep serving the last good ICS file.

Notifications

Sync emails go to the notify inbox on your dashboard (/me#notifications), not necessarily your login email. Important is the default. Critical messages (double booking, dates waiting on you, calendar import broken) always send. Operator alerts are separate.

Pending opens

When a large occupancy drop would open Airbnb (more than 5 holes or 21 nights on one listing), we hold those nights. On your dashboard or listing page, Approve — open on Airbnb removes the hold so Airbnb can open (hours of import lag). Keep blocked leaves those exact dates closed for 30 days. Smaller holes auto-open after they stay missing on a few matching syncs.

1BR didn’t open when 2BR booked

The 1BR opens only while the 2BR is occupied and the 3BR is not. Wait two successful syncs plus Airbnb import lag (hours). The 1BR must Import its own calendar URL — do not use Airbnb’s native listing-link to the 2BR/3BR, or the 2BR stay copies onto the 1BR and it stays closed. If you or an operator used Keep blocked on an earlier mass open, that applies only to those dates; a later 2BR booking should still open the 1BR.