This article explains how the Jiminny integration with Microsoft Dynamics 365 Sales works: how Jiminny connects, what it syncs and logs, and how it decides which Lead, Contact, Account or Opportunity a call is logged against. It is for Dynamics admins and Jiminny admins setting up or reviewing the integration.

Jiminny connects to Dynamics 365 Sales (online) through the Microsoft Dataverse Web API. There is nothing to install in your Dynamics environment. Dynamics 365 on-premises is not supported.

Authentication uses Microsoft Entra ID (OAuth 2.0). When you connect, you enter your organisation URL (for example https://yourorg.crm.dynamics.com) and sign in with your Microsoft account. The first time anyone in your organisation connects, a Microsoft Entra administrator has to grant consent for the Jiminny application.

What Jiminny can read and write is determined by the Dataverse security role of the connected users, not by OAuth scopes. The connected users need read access to Accounts, Contacts, Leads, Opportunities and Users, and create and update access to Appointments, Phone Calls and Tasks.

Microsoft applies service protection limits and a daily API request allowance based on your licences. Jiminny keeps its footprint small by syncing incrementally and caching a copy of the records it needs. If Dynamics reports that a limit has been reached, Jiminny pauses, waits for the period Dynamics specifies and resumes automatically.

Each user connects their own Microsoft account when they onboard. Jiminny matches each user to their Dynamics user record by email address, so the email on the Jiminny account (primary or secondary) has to match the email on the Dynamics user record.

Activities Jiminny logs are written through the user's own connection and owned by that user in Dynamics. If a user has not connected yet, Jiminny uses the integration owner's connection instead.

When a user is disabled in Dynamics, Jiminny stops matching and syncing them on the next sync. Their Jiminny account, calls and history are unaffected. If the user is re-enabled in Dynamics, Jiminny picks them up again automatically.

The integration owner is the Jiminny user whose Dynamics connection is used for metadata and record sync. This must be a Dynamics user who can read entity and field definitions, because syncing metadata requires permissions that regular users do not have.

To see whether Dynamics is connected and who owns the connection, go to Settings > Integrations. You can change the owner from the same page.

Note: If the owner's connection expires or is revoked, the owner receives an email and the integration shows as needing a reconnect in Settings. Sync does not resume until the owner reconnects.

Opportunities appear in Deal Insights with their active Business Process Flow stage, their Open, Won or Lost status and their value in the deal's own currency. Calls and emails matched to an Opportunity appear on its timeline. To choose which standard and custom fields appear, see Manage CRM Fields in Deal Insights.

You can edit fields on open Opportunities from Deal Insights and the change is saved to Dynamics through your own connection. Text, number, currency, date and option set fields are editable. Read-only, calculated and rollup fields are not.

Note: Closing an Opportunity as Won or Lost and moving it to another Business Process Flow stage are done in Dynamics, not from Jiminny.

Jiminny logs meetings to Dynamics as Appointments and calls made with Jiminny Voice as Phone Calls. Each activity includes:

Activities are saved as Completed once all content has been written. Meetings marked as internal are not logged.

To set up automatic or manual logging, see Setting up CRM Activity Logging. To log a call by hand, see Logging a call.

If you use Outlook or Exchange server-side synchronisation, Dynamics usually already has an Appointment for the meeting Jiminny recorded. Before logging, Jiminny looks for an existing Appointment for the same calendar event and, if it finds one, adds the summary and action items to it and sets Regarding if it is empty, instead of creating a second record.

This behaviour is always on for Dynamics. Updating an Appointment in Dynamics does not change the meeting in anyone's calendar or send notifications to attendees.

Jiminny identifies who is on a call and looks them up in Dynamics. How this happens depends on the type of activity.

Email matching checks all three email address fields on Contacts and Leads. If both a Contact and a Lead match, the Contact is used. Internal participants are skipped, so a call with only your own team on it is not matched.

Once Jiminny knows who was on the call, it decides which record to log the activity against. The same matching is used to associate emails with Dynamics records inside Jiminny, but only calls and meetings are logged to Dynamics.

Jiminny runs the following checks in order and stops at the first match.

Jiminny takes the customer participant's email address and looks for a matching Contact or Lead. If it finds a Lead, the call is logged on the Lead and matching stops.

If it finds a Contact, Jiminny uses the Account the Contact belongs to. If there is no Contact or Lead, Jiminny looks for an Account whose website domain matches the participant's email domain and logs the call against that Account. Free email domains such as gmail.com are never matched to an Account.

Jiminny looks at the open Opportunities on the matched Account, and any open Opportunities where the matched Contact is the customer. The list is filtered and sorted by your Opportunity matching setting first, then Jiminny takes the first Opportunity that fits:

Note: When an Opportunity is matched, the activity's Regarding field is set to the Opportunity. Otherwise it is set to the Account, Contact or Lead, in that order.

This setting controls which Opportunities Jiminny considers and how they are ordered before the checks above run. You will find it under Settings > CRM Activity Logging > Company-wide.

When you qualify a Lead in Dynamics, Jiminny picks this up on the next sync and links the Lead to the Account, Contact and Opportunity it became. Calls previously matched to the Lead carry over to those records, and future calls with the same person are matched to the Contact and Opportunity. If the Lead is disqualified, it stays in Jiminny with its history and is marked as closed.

AI CRM Filling pushes values extracted from your calls into Dynamics fields on Opportunities, Accounts, Contacts and Leads, including custom fields.

See AI CRM Filling for setup.

1. Does Jiminny write the full transcript to Dynamics?

No. Jiminny writes the AI summary and action items with a link to the call in Jiminny, where the full transcript and analysis are available.

2. Can I see Jiminny calls inside Dynamics forms, like the Salesforce app or HubSpot cards?

Not yet. Logged activities appear on the record's Timeline in Dynamics, and you open the full call in Jiminny from the link in the activity.

3. Do Dynamics Opportunities in Deal Insights show amounts in one currency?

Each deal shows its value in the currency it was created in, in the same way as Salesforce and HubSpot deals.