Quick start
From the Teamspace where you want calls to land, go to Settings → Integrations → Jiminny → Connect, paste your Jiminny API token, then create a subscription to auto-import new Jiminny calls as Recordings in this Teamspace. Jiminny exposes a JSON API suitable for server-to-server integrations; tokens are typically issued by Jiminny on request.
Why integrate with Jiminny?
Each source adds a new dimension of customer truth. Jiminny contributes the sales / customer-conversation perspective (discovery, demos, negotiations) that complements meetings, support, and survey signals already in NEXT AI—so you can analyze themes, share evidence, and drive action across your tools. Jiminny focuses on recording and transcribing calls, which makes its call objects rich in conversation context for downstream analysis.
What gets imported (object & fields)
Object in NEXT AI: Recordings in the Teamspace where you configure the integration.
Included fields (when available from Jiminny): title/subject, media, transcript text, participants/attendees, timestamps/duration, and a source link back to Jiminny (or your connected CRM). Jiminny’s data model is accessible via a JSON API for downstream systems.
Account information for every call
Connect Jiminny
Get your Jiminny API token. Jiminny issues API tokens on request (not self-served in all workspaces). Contact your Jiminny CSM/Support to obtain a token.
In NEXT AI (inside the target Teamspace): Settings → Integrations → Jiminny → Connect.
Paste the API token → Save.
Auto-import calls
Create a subscription that watches for new Jiminny calls and imports each one as a Recording in this Teamspace. The Recording keeps a source link for traceability, so teams can jump back to the original context (or CRM side-panels like the Jiminny Salesforce app, if you use it).
Continuous accounts import
Enable continuous Accounts import to keep your account directory fresh as calls arrive:
When NEXT AI ingests a Jiminny call, it matches call metadata (e.g., company name/domain) to your Accounts.
If an Account exists, we update it with the latest details; if not, we create it—so analysis and routing always sit on current account context.
You’ll see the new/updated Account linked to the Recording automatically.
Tips
Own the source of truth: Keep Jiminny for capture/coaching and use NEXT AI to combine signals across sources (sales, CS, support, surveys) into cross-functional clusters.
Close the loop from CRM: If your org uses the Jiminny Salesforce app, your Recording’s source link helps teams validate context from the account record before acting.
Scope by team (if volume is high): Start with a subset of teams or business lines, confirm value, then expand.
Troubleshooting
401/403 on connect. Ensure the API token is valid and issued for the correct Jiminny workspace; tokens are typically provided by Jiminny CSM/Support.
No calls appearing. Confirm the subscription is active and that Jiminny is capturing/processing calls for the mapped users; verify attendees/owners are mapped in Jiminny so calls are attributed correctly.
We need CRM context on the Recording. If you store summaries/links in CRM (e.g., Salesforce), the Jiminny Salesforce app surfaces Jiminny call context on account/opportunity records—use the source link to jump there.
FAQ
Q: What exactly is created in NEXT AI from Jiminny?
A Recording per Jiminny call—media, transcript text (if available), participants/timestamps, and a source link for traceability.
Q: How do we authenticate?
Paste a Jiminny API token into NEXT AI. Tokens are commonly issued by Jiminny on request (not always self-served in the UI).
Q: Can NEXT AI keep our Accounts in sync?
Yes—turn on Continuous Accounts Import so new calls create or update Accounts automatically, keeping your analysis and routing contextual.
Q: Can we validate from CRM before acting?
Yes—if you use Jiminny’s Salesforce app, you can play and analyze calls in Salesforce. NEXT AI keeps a source link so product/CX can validate context quickly.