Use Shared Find My Locations in Approved Workflows
If people already share their location with you in Find My, that data is visible to the signed-in account. Figment's Apple Connect lets an approved app read those shared locations and use them as workflow triggers — without you building new tracking infrastructure or asking anyone to install a separate app.
Design guide. Find My connector endpoint paths and scope strings are not part of Figment's current public product contract. The trigger patterns, Apple constraints, and OAuth flow described here represent confirmed design targets. Confirm endpoint availability at figment.so/apple-connect/developers before writing integration code.
What "shared location" means here
Find My's People tab shows every contact who has enabled location sharing with the signed-in Apple Account. Family members in a Family Sharing group appear automatically; the organizer's location is shared with everyone by default, while every other member individually chooses whether to participate. (Apple Support) Other contacts appear after a mutual sharing invitation.
Figment reads locations that are already visible in that tab, for the connected account. It does not create new sharing relationships, bypass consent, or surface anyone who has not actively shared with the account owner. If a contact stops sharing their location, that person disappears from the data your app can read. The connection mirrors exactly what the account owner sees in the native app.
This access operates through native connectivity on a signed-in Mac. Treat availability as dependent on current sharing settings and sync state at the time of each request.
Three native trigger conditions
Apple's Find My supports three location-notification conditions natively. (Apple Support) Those conditions are the clearest decision surface for building shared-location workflows. The table below is the core artifact of this guide — the trigger types you can reason about in your application logic, mapped directly from what Find My itself already knows how to express.
| Find My condition | Workflow trigger type | Notes |
|---|---|---|
| Arrives at a location | Arrival event | Supports one-time or recurring. Check the current Find My documentation for recurring requirements, including any per-contact approval steps. |
| Leaves a location | Departure event | Same recurring setup rules as arrival. |
| Is not at a location during a time window | Delayed-presence alert | Useful for schedule-based checks (for example, "not at school by 8:45 am"). Same recurring rules apply. |
Your app does not reproduce Apple's notification system. It reads shared location data and applies its own condition logic based on the data it receives. One practical limit: a user account supports up to 25 "Notify Me" notification slots across all friends in the native app. (Apple Support) This feature is designed for a personal network, not bulk location monitoring.
Authorize the connection
Before your app can read Find My data, the user authorizes a connection through Figment's hosted consent screen using PKCE. The flow uses GET /apple-connect/authorize with client_id, redirect_uri, response_type=code, the requested scope, state, and a code_challenge (S256). After approval, exchange the code at POST /api/apple-connect/oauth/token. The response includes an access_token (valid 900 seconds), refresh_token, and connection_id.
The developer app never receives the user's Apple password. Register at figment.so/apple-connect/developers to get a client_id. The OAuth for iCloud overview covers the full PKCE flow and consent model.
Workflow patterns you can build
These are integration design patterns. Because Find My endpoint paths are not yet in the public product contract, treat them as design blueprints rather than copy-paste implementations.
Family coordination assistant. An agent reads the People list each morning and checks whether family members are at their expected location — school, office, a relative's home. The delayed-presence condition ("not at school by 8:45 am") drives an alert rather than a manual check-in call.
Logistics confirmation. A small business owner tracks a delivery driver who already shares their location. When the driver arrives at a delivery address, the app logs a timestamped receipt automatically — no polling a third-party GPS service, no SMS parsing.
Care coordination. When a family member's location transitions from home to a medical center, the app updates a shared note so other family members see the change without anyone needing to send a manual message.
None of these patterns require new software on the shared contact's device. They use location data that person already chose to share.
What this cannot do
No arbitrary tracking. You can only read locations of people who have shared with the connected account. There is no search API for Apple users by name or phone number.
No new sharing invitations from code. Your app cannot invite someone to share their location. That step happens in Find My directly, before your workflow runs.
Not guaranteed real-time. Access operates through a Mac-native connection and reflects sync state. Treat locations as eventually consistent, not a live GPS feed. Live Location (direction and speed) requires both parties to have an iPhone with iOS 15 or later and is a separate sync layer. (Apple Support)
Devices and items are a different scope. AirTags, iPhones, and other owned devices appear under a device scope, not a people scope. See Connect Find My Devices to an Assistant.
Home presence triggers are a different system. HomeKit automation can also fire on arrival and departure using a Home hub and device-based geofencing — entirely separate from Find My people sharing. See Give an Agent Permission to Run Home Scenes and Review Home Camera Events with an Assistant.
Get started
Connect Apple Account to begin building against your own data. The OAuth for iCloud overview explains how scope grants work across Apple services.
