Calendar
Planning scheduled transport around Outlook
Renaro's GA release supports dispatch-owned schedules, exports, and webhooks. Direct Microsoft OAuth authorization is not presented as a shipped connector.
- Corporate
- Business travel context
- Reservations
- Scheduled bookings
- Dispatch
- Assignment state
- Finance
- Booking-level payment context
Calendar-aware, dispatch-owned
Calendar views can help teams see scheduled work without making calendar edits the source of operational truth.
- Use supported exports or webhooks for downstream planning.
- Keep dispatch changes, passenger updates, and payment state in Renaro.
- Do not rely on a direct Microsoft OAuth connector until its callback and external evidence are complete.
Where this page fits
Outlook pages serve corporate and executive transportation buyers that operate around Microsoft-based workflows.
- Link to corporate transport, executive transport, and booking management.
- Use provider-specific calendar pages to improve integration discoverability.
- Keep calendar claims tied to scheduled transportation operations.
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.