Calendar
Planning scheduled transport around Google Calendar
Renaro's GA release keeps scheduled work in the booking system and supports exports and webhooks. Direct Google OAuth authorization is not presented as a shipped connector.
- Reservations
- Advance booking context
- Chauffeurs
- Assignment visibility
- Accounts
- Corporate context
- Airports
- Pickup timing
Calendar visibility without losing dispatch control
Calendar views can support planning, but dispatch still needs status, driver, fare, passenger, and payment context in the authoritative booking record.
- Use supported exports or webhooks for downstream planning while preserving booking ownership.
- Connect assignments and passenger context to the operating record.
- Do not rely on a direct Google OAuth connector until its callback and external evidence are complete.
Where this page fits
Calendar searches are common for chauffeur, executive transportation, and small fleet buyers.
- Link calendar content to chauffeur, executive, quote, and booking pages.
- Use this page to capture scheduling-oriented search intent.
- Avoid making calendar the system of record for trip state.
Related integration paths
Common questions
Are integrations implemented directly in the landing app?
No. The Astro landing app documents and routes SEO traffic to Renaro's product areas. Operational integrations are owned by the API, worker, and platform domains.
Why create integration landing pages?
Operators and technical buyers search for specific provider support. These pages state the current data and workflow boundary and link to capabilities that are available today; they do not imply that an unconfigured OAuth connector is live.
See Renaro with your own trips.
Bring a few of your real reservations. We'll show you how your office would handle them in Renaro, from the first phone call to the paid invoice.