Connect the calendar where iOS expects it
On current iPhone settings, look under Apps, Calendar and Calendar Accounts to add or inspect the account. Settings labels can differ with the iOS version. Choose Google through Apple’s account flow, complete its authentication yourself and enable Calendar for that account.
Then open Apple Calendar. Find one event on a known date before returning to Nowhop. Apple’s Calendar account settings guide is the reference for this device-level setup.
Separate three different connections
The Google Calendar app can display an account that you have not enabled for Apple Calendar. Seeing an event in Google’s own app therefore does not prove that another iOS app can read it through the system calendar store.
Nowhop uses that system store with permission. It does not ask for your Google password, create a separate Google OAuth token or inspect confirmation emails. If a managed work account restricts system access, follow the organization’s permitted setup rather than assuming the importer can bypass it.
Import only what the day needs
Once the event appears in Apple Calendar, open Nowhop’s calendar import, choose the relevant calendar names and review the day’s events. Select a small set first. Check all-day entries separately from appointments with a start time, especially around a trip.
Calendar names are the selection unit before individual events. Custom colors on separate Google events are not promised as separate import labels. The goal is a readable Plan, not a second copy of every calendar you can access.
Understand what happens after a change
The imported event becomes a local Plan copy. If the organizer moves the original meeting, check it in the source calendar and update the plan you rely on. Removing a Google account from iPhone settings is not a reliable way to remove already copied local records.
This development workflow is deliberately narrower than live Google synchronization. Apple’s EventKit documentation explains system calendar access; it does not turn a one-time import into a background sync service.
Questions this guide answers
Do I need to sign into Google again inside Nowhop?
No separate Nowhop Google login is part of this flow. Account authentication belongs to iPhone Calendar setup; Nowhop asks for iOS calendar access when you use import.
Why does Google Calendar show an event that Nowhop does not?
Check whether the account and calendar are available in Apple Calendar, not only Google’s app. Then check the date, selected calendar names and reading permission.
Will editing Plan send an invitation update?
No. Plan is a local copy in the current implementation. Use the original calendar to change an invitation or notify attendees, then reconcile your local plan.
Are every Google account and notification scenario verified?
No. Simulator tests do not establish every real iPhone account, shared-calendar restriction or notification delivery path. Physical Google and iCloud account checks remain release gates for the development build.
Sources & scope
Official pages reviewed for this guide on October 31, 2026. Features and availability can change; check the linked provider before choosing.
Nowhop behavior is based on our implementation specification. Public demos use samples. Read our editorial approach.
See how a day comes together.
Try the Nowhop preview ↗Sample data. No sign-up or location access.