Software factory: Customer integrations
Let each person who signs in to your app connect their own accounts: Google, Apple, Zoom, Granola, or any app you add.
Customer integrations let each person who signs in to your app connect their own accounts. Your app reads and writes only that person’s data. Chipp handles every sign-in, so you set up nothing: no client ID, no client secret, no API key.
Open your project and go to Customer integrations. Each integration has an On or Off switch.
Three ways a person connects
| Kind | Examples | How the person connects |
|---|---|---|
| Gmail, Google Drive, Google Calendar, Google Sheets | Google’s own sign-in screen. | |
| Apple | Apple Calendar, iCloud Mail | A Chipp page where they enter their Apple ID and an app-specific password. Your app never sees it. |
| Other apps | Zoom, Granola, and any app you add (HoneyBook, Dubsado, Jobber, and more) | That app’s own sign-in. |
Granola
Granola connects through Granola’s own MCP server. Each person signs in with their own Granola account and approves access. Chipp registers itself with Granola automatically, so nobody types an API key or a client secret.
Turn on Granola under Other apps. Then:
- Each person selects Connect in your app and signs in to their own Granola account.
- Your app sees the Granola tools that person’s plan has. The list can differ from person to person.
- Your app gets only the notes that person can see in their active Granola workspace. Workspaces are never combined.
- A person can reconnect or disconnect at any time. Disconnect deletes their stored sign-in and removes their Granola tools from your app.
What each Granola plan allows:
- Basic (free). Notes from the last 30 days, with fewer tools.
- Business. Full note history, under Granola’s policy.
- Enterprise. The person’s Granola admin chooses the note scopes. If the admin turned off MCP access, the person sees this message: “Your Granola admin needs to enable MCP access in Settings -> Workspace -> General -> Apps & connectors -> MCP access.” They also learn they can connect with a Granola API key instead.
If a person’s access was revoked or expired, they see Needs reconnect, not an error.
Three separate Granola connections
Granola can reach your project in three different ways. They never share a credential.
| Connection | Where | Who signs in |
|---|---|---|
| Customer sign-in (this page) | Customer integrations | Each person who uses your app, with their own account. |
| Builder-level Granola MCP | The Brain page, Integrations | You, once, for your own agent. |
| Granola API key | The Granola integration | A shared workspace credential. |
Turning one off never changes the others.
Turn it off
Switch an integration off and people can no longer connect it. Your app can no longer use anyone’s connection, and Connect disappears. People who connected earlier stay stored, so turning it back on restores them. Each person can still disconnect their own account.
See who connected
Who connected lists every person’s own connection. Filter by person or by integration. Select Disconnect on a row to remove that person’s connection.
Wire it into your app
A switch alone changes nothing in your app’s code. After you turn an integration on, select Wire it into my app. The AI Engineer adds a Connect button for each signed-in person and uses only that person’s account. Then test it with two different people and check that each one sees only their own data.