Apple Calendar can subscribe to an iCal URL generated from Airtable. The resulting calendar is read-only: changes come from Airtable, and Apple Calendar provides the display, device sync and notifications.
Build a calendar-safe Airtable view
Start with a view that contains only the records intended for subscribers. Map a title and start date, then add the event details your audience needs.
For example, a field-service feed might map:
- Job reference to the event title
- Arrival and completion times to the event range
- Site address to the location
- Work-order link to the event URL
Keep internal notes and private customer data outside the mapping. A calendar should be a deliberate delivery surface, not a copy of the base.
See the full field-service calendar pattern for a practical setup.
Subscribe on iPhone or iPad
Apple's current instructions for iOS 26 and iPadOS 26 are:
- Open Calendar and tap Calendars.
- Tap Add Calendar.
- Choose Add Subscription Calendar.
- Enter the private Airtable feed URL.
- Choose a name, color and the iCloud account.
- Finish the subscription.
On earlier iOS versions, the labels differ slightly, but Apple still uses an Add Subscription Calendar flow. The official steps are maintained in Add calendar subscriptions in iCloud.
Choosing iCloud as the account makes the subscription available across devices signed in with the same Apple Account.
Subscribe on Mac
In Calendar on macOS:
- Choose File > New Calendar Subscription.
- Paste the feed URL.
- Select Subscribe.
- Set its name, color and location.
Apple documents the same process in Subscribe to calendars on Mac.
What happens when Airtable changes
The calendar application requests the subscription again and replaces its representation with the current feed. You cannot use Apple Calendar to update the Airtable record.
That one-way behavior prevents conflicts and keeps dispatch, editorial or project data authoritative in Airtable. If write-back is required, read Airtable to Calendar vs Unito before selecting a two-way system.
The feed URL is a bearer secret. Do not publish it on a website or place it in a public document. If it leaks, delete the feed and create a replacement URL.