Skip to main content
Setting up the Jiminny integration

You can sync call recordings and summaries from Jiminny into Planhat, using our Jiminny integration

Carly Hammond avatar
Written by Carly Hammond
Updated over a week ago

Summary

  • Data you can sync

    • Sync Jiminny call recordings, AI summaries and selected call data into Planhat as Conversations

  • Sync direction

    • One direction: from Jiminny to Planhat

  • Sync frequency

    • The sync runs once an hour, and brings in calls from the previous hour

  • Data mapping

    • Jiminny call recording records are synced to the Conversation model in Planhat

    • For field mapping, see tables below

Who is this article for?

  • Planhat users who are interested in syncing Jiminny data to Planhat

Article contents


Introduction

If you use Jiminny for conversation intelligence, then you'll likely want to sync customer calls into Planhat. With Planhat, you can compile, organise and analyse all your customer data, from various sources, giving you a full 360-degree view of your customers. With Jiminny data in Planhat, you will save your CS team time by automatically summarising calls, and ensure that call recordings are accessible alongside other customer data.

The Jiminny integration is a "light" integration, which does not have its own settings or configuration page. Setup requires a small amount of work by a Planhat Technical Account Manager (TAM). The data it syncs in is defined below and cannot be modified.

Once configured, Planhat will request data from Jiminny, which will be brought into Planhat on the Conversation model, populating the subject, the description, the Conversation Type ("Jiminny Call"), and a series of other fields. Some additional fields (custom fields) will be added to the Conversation model to house Jiminny data, and conditionally hidden from other Conversation types (so Jiminny-specific fields don't show on your Zendesk tickets or Intercom chats, for example).

Synced calls from Jiminny will look similar to this:

(You can click the image above to view it enlarged. The grey boxes are where customer information has been hidden for the image.)


Data mapping

Planhat model

Sync direction

Jiminny

Conversation (type "Jiminny Call")

From Jiminny to Planhat

Call

Planhat system field

Jiminny field

Definition

companySourceId

crmId

The shared Company CRM ID in both Jiminny and Planhat

subject

title

The title of the call

summary

actionItems & summary

The AI summary and action items of the Jiminny call

endusers

endusers

External people present in the call

users

users

Internal people present in the call

date

scheduledStartTime

Start time of the call

externalId

id

The Jiminny call ID

Planhat custom field

Jiminny field

Definition

Jiminny Call URL

N/A

URL to the call page in Jiminny (URL field type)

Call Duration

durationMinutes

Call length in minutes (number)

Talk Duration

talkDurationMinutes

Minutes talked (number)

Customer Talk Duration

customerTalkDurationMinutes

Minutes the external people spoke (number)

User Questions Count

userQuestionsCount

Count of questions asked by internal people (number)

Customer Questions Count

customerQuestionsCount

Count of questions asked by external people (number)

Call Themes

uniqueThemes

Themes discussed during the call (multipicklist of your Jiminny call themes)

Get Jiminny Summary

N/A

You can toggle this on to manually fetch data from Jiminny if required (checkbox)


How does the sync work?

The sync works via Planhat Automations and the Jiminny API.

Planhat triggers a request to the Jiminny API every hour. It syncs in calls made during the last hour in Jiminny, filtering and saving only those where the Jiminny CRM ID matches a Company Source ID in Planhat. This is how it maps calls to the correct Company in Planhat.

📌 Important to note

Both Jiminny and Planhat should be connected to the same CRM (e.g. Salesforce or HubSpot). This is so we can map Jiminny calls to Planhat Companies via the CRM ID ("Source ID" in Planhat).

The retrieved calls are stored as new records of the Conversation model in Planhat, with the custom Conversation Type "Jiminny Call".

For each new Conversation, Planhat makes an additional request to Jiminny to retrieve the AI summary and action items. If the AI summary and action items are not available at the time of the request, you can manually retrieve this information later by toggling the “Get Jiminny Summary” button on the Conversation in Planhat.


Setting up the integration

If you would like to sync Jiminny calls to Planhat, please reach out to your Planhat TAM, and they will set up the integration for you.

You will need to obtain an API token from Jiminny. This is not available from the UI; please contact your Jiminny CSM or Support at Jiminny (support@jiminny.com) to get one.

We will need the API token to make requests to the Jiminny API, which is how we retrieve the call data.


Troubleshooting the integration

The Jiminny sync is relatively straightforward: we are requesting information from Jiminny, and saving it in Planhat.

A couple of key points to note, so you know what to expect:

  • The Jiminny integration will not sync historic calls; once live, it will start syncing calls going forwards

  • Any updates made in Jiminny after the call has been synced to Planhat will not be reflected in Planhat

If data does not sync into Planhat and you think it should have:

  • If the AI summary and action items do not sync into the Planhat Conversation, this is likely because they were not available when Planhat requested them. Simply toggle the "Get Jiminny Summary" button (shown above) to manually trigger retrieval of this information

  • If you have issues with missing data, please reach out to Jiminny Support (support@jiminny.com) or your Jiminny CSM for troubleshooting. Planhat does not control what data is sent, and there are not detailed logs on the Planhat side


Jiminny calls within Planhat

Jiminny calls are stored in Planhat as Conversations with the custom Conversation Type "Jiminny Call".

You can view the calls themselves on Company and End User Profiles, as well as in the Conversations Module. It's easy to apply filters. To see all and only Jiminny calls, just select this as the "Type".

In the Conversations Module, you can even build more advanced filters based on other fields/properties too.

You can comment on Jiminny calls in Planhat - to tag in other colleagues, for instance.

In addition, within the "Metrics" tab of the Data Module, Jiminny call volumes can be saved as time-series data (under the "Conversations" category). You can build on this raw time-series data with Calculated Metrics - for example, tracking trends over time. In Pages (in the Customer Intelligence Module), you can create graphs to analyse and visualise time-series data.

Did this answer your question?