How to let a user connect their accounts

Your app's AI works best when it can see what the person already has in other tools. Those tools sit outside your app.

A connected account lets the person grant that access by approving a link. The app's developer starts the connection from the server.

Your server calls POST /v1/context-sources/{provider}/connect for a provider. The person connects their own account by approving a link.

Supported providers are gmail, calendar, drive, notion, slack and email_bridge. Gmail, Calendar and Drive connect once Harny has approved Google access for your app. You request that in the console.

Sync, list and disconnect exist for connected accounts. Disconnect (DELETE /v1/context-sources/{provider}) ends your app's access. For gmail, calendar, drive, slack and notion, the grant at the provider is revoked too.

Connected sources are read with POST /v1/context/assemble, which returns ranked context from the person's memory and their connected sources, scoped to that person.

1. Request Google access for your app in the console if you plan to use gmail, calendar or drive.
2. From your server, call the connect route for the provider the person chose.
3. Give the person the link. They approve access to their own account.
4. Sync the connected account.
5. List the person's connected accounts to show what is connected.
6. Let the person disconnect an account they no longer want shared.
7. Call POST /v1/context/assemble for that person to read their connected sources.

• Gmail, Calendar or Drive will not connect until Google access is approved for your app.
• The person connects their own account by approving the link.

Nadia at Acme wants the Acme pilot assistant to read her calendar. Her user id is demo-user. Your server calls the connect route for the calendar provider, and Nadia approves the link.

After that, your server can read her connected calendar with POST /v1/context/assemble for demo-user. Disconnect is available if she no longer wants the calendar shared.