Skip to main content

Import Jiminny calls

Quick start​

Connect Jiminny in NEXT, enable the Teamspace subscription for this import, and let the scheduled sync pull Jiminny call activities into NEXT as Recordings.

Why integrate with Jiminny?​

Jiminny captures revenue conversations that are often full of objections, decision criteria, and deal risk signals. Pulling those calls into NEXT makes that commercial voice-of-customer data available alongside product and support feedback.

  • It helps teams understand what customers say in live revenue conversations.
  • It brings call evidence into the same analysis environment as surveys, tickets, and reviews.
  • It reduces the gap between enablement tooling and product-learning workflows.

What gets imported​

  • Object in NEXT: Recordings
  • Source objects: Jiminny call activities
  • Included fields: Call title, media or transcript data when available, call timing, speakers, and source identifiers.

Authentication​

Jiminny API credentials configured for the integration.

Connection notes​

  • Connect Jiminny with the credentials issued for your workspace.
  • Enable the Teamspace subscription that should import the selected calls.

Configuration notes​

  • Imports are incremental and only fetch activity updated after the previous successful sync.
  • Use the subscription configuration to keep the import scoped to the Teamspace that needs those calls.

Limitations​

  • Available metadata depends on the Jiminny API response for each call.
  • Only calls visible to the configured API credentials can be imported.

Troubleshooting​

  • If imports stop, verify the Jiminny credentials are still valid.
  • When calls are missing, confirm the source activities fall after the subscription start timestamp.

FAQ​

Are imported Jiminny calls stored as Highlights?​

No. They are stored as Recordings in NEXT.

Can I backfill older calls?​

Yes. Adjust the subscription window or rerun the import from an earlier timestamp.