Connecting Grain to OttoKit

Overview

To connect your Grain account with OttoKit, you need a Client ID and Client Secret. These credentials let OttoKit securely access your Grain data, like recordings, transcripts, and AI-generated summaries, on your behalf.

Grain does not currently offer a self-serve developer portal to create these credentials. You must request them directly from the Grain team. This guide walks you through the full process from start to finish.

What you’ll need

• An active Grain account with admin or owner access to your workspace
• Your OttoKit account ready (you’ll need the redirect URI from OttoKit in Step 2)
• Around 1 to 3 business days for Grain to respond to your request

Step 1: Get your OttoKit redirect URI

Before you reach out to Grain, you need the redirect URI that OttoKit uses for OAuth callbacks. Grain requires this to register your application.

1. Log in to your OttoKit account at ottokit.com
2. Go to Connected Apps and search for Grain
3. Click Connect on the Grain integration card
4. Copy the redirect URI shown on the connection screen, it will look something like:

https://api.ottokit.com/grain/connection

Keep this tab open or save the URI somewhere handy. You’ll send it to Grain in the next step.

Step 2: Request credentials from Grain

Since Grain’s API is currently in a partner-access phase, you need to email their team to request OAuth credentials. Send a request that includes the following details so they can register your application quickly.

Who to contact

Email Grain’s support or developer team at [email protected] and mention you need OAuth2 API credentials for an integration with OttoKit.

What to include in your request

Field	What to send
Application name	OttoKit Integration (or your workspace name)
Use case	Connecting Grain with OttoKit to automate workflows based on recordings, highlights, and meeting events
Redirect URI prefix	The URI you copied from OttoKit in Step 1
Workspace email	The email tied to your Grain workspace
Application type	Server-side (so you receive both a Client ID and Client Secret)

Sample email template

Subject: Request for OAuth2 API credentials for OttoKit integration.
Body: Hi Grain team, we would like to request OAuth2 API credentials (Client ID and Client Secret) to build an integration between Grain and OttoKit, a workflow automation platform. Details:  Application name: OttoKit Integration, Application type: Server-side (web), Redirect URI prefix: https://app.ottokit.com/authorize/grain, Workspace email: [email protected], Use case: Allow Grain users to trigger automations in OttoKit when recordings are added, updated, or tagged, and to push Grain data into downstream apps like CRMs, project management tools, and notifications.
Thanks,
Your Name

Note Grain typically replies within 1 to 3 business days. They may follow up with a few clarifying questions about your use case before issuing credentials.

Step 3: Receive and store your credentials

Once Grain approves your request, they will share two values with you:

Credential	Description
Client ID	A public identifier for your application. Used in the OAuth authorization URL.
Client Secret	A confidential key. Never share it publicly or commit it to a repository.

Note Treat your Client Secret like a password. Anyone with this value can act as your application. If you suspect it has been exposed, contact Grain immediately to rotate it.

Step 4: Add the credentials to OttoKit

Now plug the credentials into OttoKit to finish the connection.

5. Go back to the Grain connection screen in OttoKit from Step 1
6. Paste your Client ID into the Client ID field
7. Paste your Client Secret into the Client Secret field
8. Click Connect
9. You will be redirected to Grain to sign in (if you aren’t already) and approve the OAuth connection
10. Once you confirm, Grain will redirect you back to OttoKit, and your connection will be active