What the connection does
- One-click OAuth. You authorise Lemon in Hospitable; Lemon parks the authorisation, completes sign-in, and shows you the property list with a consent step before importing anything.
- Reservations by webhook, with a 30-minute poll as a backstop. A new booking, a change or a cancellation reaches Lemon in seconds, as an explicit event — not inferred from a calendar's absence.
- Per-property source. A property is either on iCal or on Hospitable; when you connect it, Lemon deactivates its iCal feeds so the two never fight.
- Privacy by design. Reservation payloads are scrubbed at ingest: Lemon keeps dates, status, platform and a reference, not the guest's contact details.
- Migration you can watch. The import runs as a durable job with honest progress and recovery if it is interrupted.
Things worth knowing
- Hospitable's
on holdstatus covers two different situations; Lemon documents both and handles them so a held reservation does not create a phantom clean. - Lemon does not write back to Hospitable. Cleaning lives in Lemon; Hospitable stays the system of record for the reservation.
- Importing Hospitable's own cleaning checklists into Lemon is planned and depends on an additional API scope.
Why not just use Hospitable tasks?
Tasks tell a cleaner a job exists. Lemon runs the cascade when they do not answer, requires a photo per room, tracks supplies, handles the payout, and keeps the audit trail — and it does so over the channel the cleaner already reads, without an app.