Changelog¶
[1.1.0] — 2026-03¶
Added¶
- Communication engine: automatic scheduling of emails (confirmation, welcome, check-in reminder, thank you, loyalty)
- Communication rules (
airdoo.comm.rule): per-accommodation rules and default rules with priority - Communication logs (
airdoo.communication.log): full send tracking with idempotency - Crons: Generate Communications (4h) and Send Due Communications (10 min)
- Seasonal pricing: direct booking calculation via Odoo pricelist night by night
- Contact Form API: endpoint
/api/v1/airdoo/contact-leadfor web forms → CRM - Health Check API: endpoint
/api/v1/airdoo/healthfor monitoring - Webhooks:
/airdoo/webhook/updateand/airdoo/webhook/calendar_sync - Weather integration: latitude/longitude fields + OpenWeather API on accommodations
- Accommodation branding: logo, signature, social media links, manager title
- WhatsApp: WhatsApp Business number and URL fields
Changed¶
- API authentication: migrated to Bearer Token (
auth='bearer') — replaces X-Odoo-API-Key - Calendar API: endpoint migrated to
/api/v1/airdoo/calendar(POST) — replaces/airdoo/api/calendar(GET) - Cleaning
.icsinvitations: multilingual support (FR, EN, ES, DE, IT, PT)
[1.0.0] — 2025-Q4¶
Added¶
- Gmail sync: automatic parsing of Airbnb emails via Google OAuth2
- Reservation model:
sale.orderextension with PMS fields (checkin, checkout, guests) - Guest composition: adults, children, babies
- Multi-accommodation management:
airdoo.accommodationwith calendar colours - Cleaning mission: automatic email +
.icsinvitation to the cleaner - REST API v1: availability, bookings (CRUD), calendar
- Deprecated API: old endpoints redirected to v1
- Dashboard: KPIs for revenue, nights, occupancy rate
- Gantt calendar view: reservations by accommodation with colour coding
- Email templates: confirmation, welcome, thank_you, cleaning mission
- Advanced parser: configurable parsing rules (
airdoo.parsing.rule) - Ignored emails: tracking of unprocessed emails with reason
- Parsing errors: detailed log of extraction errors
← Back: FAQ