Hospitable direct connection

How the connection works

1. Settings → Integrations → Hospitable → Connect. You authorise Lemon in Hospitable (OAuth with refresh tokens).
2. Lemon shows the properties Hospitable returns and asks for consent before importing.
3. The import runs as a durable, resumable job with visible progress. Each imported property is set to bookingSource: hospitable and its iCal feeds are deactivated by the integration, so the two sources never disagree.
4. From then on, reservation webhooks create, move and cancel bookings; a 30-minute poll catches anything a webhook missed.

What Lemon keeps from a reservation

Dates, status, platform, guest count and the reservation code. Guest names and contact details are dropped at ingest — Lemon schedules cleaning and does not need them. This is documented for the integration's data-processing review.

Statuses and edge cases

• on hold in Hospitable covers two situations (a reservation awaiting confirmation and an inquiry-type hold). Lemon distinguishes them so a hold does not create a phantom cleaning job, and releases the job when the reservation confirms.
• Cancellations are explicit events, so there is no confirmation window to wait through.
• Lemon does not write back to Hospitable. Cleaning lives in Lemon.

Planned

Importing the property's Hospitable cleaning checklist into Lemon's per-property checklist — waiting on an additional API scope.