What the connection does
- One-click connection. You approve Lemon in Hospitable. Lemon completes sign-in and shows you the property list, with a consent step before importing anything.
- Reservations arrive in seconds. A new booking, a change or a cancellation reaches Lemon as a clear event, not guessed from a booking missing from a calendar.
- One source per property. A property gets its bookings either from its calendar links or from Hospitable. When you connect it, Lemon switches off its calendar links so the two never clash.
- Privacy by design. Lemon keeps the dates, status, platform and a reference, not the guest's contact details.
- An import you can watch. You see honest progress, and the import recovers if it is interrupted.
Things worth knowing
- Hospitable's "on hold" status 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 extra access from Hospitable.
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.
Technical details
- The connection is one-click OAuth: Lemon parks the authorisation, completes sign-in, then shows the property list with a consent step.
- Reservations arrive by webhook, with a 30-minute poll as a backstop.
- Per-property source: a property is either on iCal or on Hospitable; connecting it deactivates its iCal feeds.
- Reservation payloads are scrubbed at ingest.
- The import runs as a durable job with progress reporting and recovery if it is interrupted.
- Hospitable's status is
on hold. Checklist import depends on an additional API scope.