Skip to content

Integrations

Connect the tools your business already uses.

NLDONA connects calendars, email and approved company knowledge so customer interactions can use the right context — without turning external providers into business authority.

Google CalendarMicrosoft CalendarGmailGoogle Drive

NLDONA

NLDONA

Calendar
Availability context
Gmail
Inbound inquiry / draft flow
Drive
Approved business knowledge

Supported integrations today — not a marketplace catalog.

Connected tools

Your tools, connected to one business system.

Connected apps provide context and delivery. NLDONA keeps the business state governed.

Four integrations today

Google Calendar, Microsoft Calendar, Gmail and Google Drive — nothing else is claimed as connected yet.

Providers stay connected services

External systems inform, constrain and deliver. They do not silently become NLDONA’s booking or customer authority.

Scoped connection

Authorised users connect what the business needs through Connected Apps in the Control Plane.

More integrations are added deliberately. If it is not on this list, it is not connected yet.

Calendars

Keep external busy time connected to NLDONA scheduling.

External calendars help prevent conflicts — they do not become another booking system.

Google Calendar

Connect Google Calendar so selected calendars can contribute busy-time constraints to NLDONA availability.

  • OAuth connection with selected calendars
  • External busy time can constrain available slots
  • NLDONA bookings can be projected outward as calendar events
  • Booking truth remains in NLDONA

Microsoft Calendar

Bring Microsoft Calendar into the same scheduling picture as Google Calendar.

  • OAuth connection for Microsoft 365 calendars
  • External busy time in the same booking picture
  • NLDONA bookings can be projected outward where configured
  • Providers do not silently redefine NLDONA schedule authority

One availability picture

Google busy time and Microsoft busy time can sit beside NLDONA’s schedule so customers and staff see coherent availability.

  1. Google busy time
  2. Microsoft busy time
  3. NLDONA schedule
  4. Available slots
  5. NLDONA booking → projected outward

External busy time is a constraint. NLDONA remains the business scheduling system — provider event IDs are locators, not a second booking core.

Gmail

Turn important business email into something your team can act on.

Selected Gmail workflows bring inbound business requests into NLDONA — with human confirmation before send.

Inbound inquiry

A business email arrives through the connected Gmail workflow.

Needs Reply

NLDONA surfaces items that still need a person.

Draft assistance

Your team can review a draft before anything is sent.

Confirm & send

Human confirmation remains required before NLDONA sends.

NLDONA is not a full Gmail client. Mailbox-wide search, mass outbound mail, campaigns and unattended outbound replies stay out of scope.

Gmail here is your business mailbox workflow. NLDONA System Transactional Email (account, security and billing notices) is a separate system.

Google Drive

Use approved company files as business knowledge.

Selected and approved files can contribute to NLDONA’s governed business knowledge.

Connect Drive

Authorised users connect Google Drive through Connected Apps.

Select files

Choose the company documents that should be considered.

Review & approve

Knowledge is reviewed under your business control model.

Answer with context

NLDONA can use approved knowledge when helping customers.

NLDONA does not index Drive wholesale, auto-trust every file, or edit/delete Drive files as business authority.

Connection health

Know when a connection needs attention.

NLDONA surfaces connection problems that may affect business workflows.

Operational

Connected and ready for supported workflows.

Needs setup

Connection is not finished yet.

Disconnected

The app is not connected.

Re-authentication required

The connection needs to be refreshed.

Degraded

The connection is impaired and may need attention.

Action required

A person should review the Connected Apps status.

Connect, reconnect and disconnect under control

Authorised users can manage connected apps from the Control Plane.

  • Connect supported apps
  • Choose relevant calendars or files where supported
  • Reconnect when access expires
  • Disconnect when the business no longer needs the link

Statuses are tenant-facing connection and readiness signals — not provider infrastructure telemetry, tokens or raw webhook errors.

How it works

Connected apps support the workflow. NLDONA keeps the business state consistent.

Providers contribute context and delivery. NLDONA validates and records governed business outcomes.

01

Customer asks

A request arrives on a supported channel.

02

NLDONA understands

Conversation stays under AI — decisions stay governed.

03

Connected app helps

Calendars, Gmail or Drive contribute context or delivery.

04

NLDONA validates

Business state is checked against NLDONA authority.

05

Outcome

Bookings, replies and knowledge stay in the governed system.

Google / Microsoft Calendar

Busy constraints and outward booking projection.

Gmail

Inbound inquiry, Needs Reply, draft and confirm-send.

Google Drive

Selected approved files as governed knowledge.

Connect only what the business needs.

Explicit connection

Apps are connected deliberately — not assumed.

Scoped access

Provider access stays limited to what the workflow needs.

Selected resources

Calendars and files can be chosen where the product supports selection.

Governed access

Tenant permissions decide who can manage connections.

FAQ

Common questions about NLDONA Integrations.

Short answers based on current product truth.

Which integrations does NLDONA support?

Google Calendar, Microsoft Calendar, Gmail and Google Drive. Anything not on that list is not connected yet.

Does NLDONA integrate with Google Calendar?

Yes. Google Calendar can contribute external busy time to NLDONA availability, and NLDONA bookings can be projected outward as calendar events. Booking truth remains in NLDONA.

Does NLDONA integrate with Microsoft Calendar?

Yes. Microsoft Calendar availability can sit in the same booking picture, with outward projection where configured. Providers do not become a second booking system.

Can external calendar events block availability?

Yes. Connected calendars can contribute busy-time constraints so NLDONA helps prevent double-booking.

Can NLDONA add bookings to my calendar?

Yes. NLDONA can project canonical bookings outward to connected Google or Microsoft calendars. The booking remains governed in NLDONA.

Does NLDONA integrate with Gmail?

Yes, for selected business email workflows: inbound inquiry evidence, Needs Reply, draft assistance and human confirmation before send.

Can NLDONA send email automatically?

Outbound Gmail replies need human confirmation before NLDONA sends. NLDONA is not an email marketing platform.

Can NLDONA use Google Drive files?

Yes. Selected Google Drive files your business approves can become governed knowledge for answers.

Does NLDONA import my entire Google Drive?

No. NLDONA does not auto-index Drive wholesale or auto-trust every file as business truth.

What happens if an integration disconnects?

NLDONA can surface connection problems such as disconnected, re-authentication required or degraded states so your team can reconnect from Connected Apps.

Can connected apps change NLDONA business data directly?

No. Connected apps provide context and delivery. Provider events and IDs do not silently redefine NLDONA’s booking or customer authority.

Does NLDONA support Apple Calendar or CalDAV?

No. Apple Calendar and CalDAV are not current public integrations.

Does NLDONA support Google Actions Center?

No. Google Actions Center / Reservations End-to-End is not claimed as a live public integration here. Google Calendar integration is separate.

Try NLDONA

See how NLDONA could connect the tools your business already uses.

Paste your public website to start a temporary demo under your review.

Public information only. Demo experiences stay isolated from Production.