Nylas is calendar infrastructure. Orita is provider resolution infrastructure. They solve different problems — and for some applications, you need both.
Connects to Google Calendar, Outlook, and Exchange. Reads and writes events across user accounts. Best when calendar synchronization is the core problem.
Searches a provider network, applies eligibility rules, resolves availability, returns ranked explained options, and safely confirms the booking. Best when you must determine who should handle a request.
Some applications use Nylas and Orita together: Orita resolves which provider is eligible and available, then Nylas writes the confirmed event to the provider's calendar.
// 1. Orita resolves the right provider
const resolution = await orita.resolveScheduling({
serviceId: "svc_therapy",
constraints: { languageCodes: { anyOf: ["es"] } },
dateRange: { from: "2026-08-05", to: "2026-08-12" }
});
// 2. Patient approves → confirm with Orita
const booking = await orita.confirmResolution(
resolution.resolutionId,
{ optionId: resolution.options[0].optionId, customer }
);
// 3. Nylas writes to the provider's calendar (optional)
await nylas.events.create({
calendarId: providerCalendarId,
title: booking.title,
when: { startTime: booking.startUtc, endTime: booking.endUtc }
});If your application already knows the provider — use Nylas or any calendar API. If it must determine who is eligible and available, that's Orita.