Skip to main content

How Modjo x Salesforce works

A clear overview of data exchanges between Modjo and Salesforce.

Updated this week

1. Why integrate Salesforce with Modjo?

The Salesforce ↔ Modjo integration allows you to centralize all commercial interactions across both platforms.

By connecting your CRM to Modjo, you benefit from:

  • Complete tracking of your calls and meetings.

  • Quick access to key information (summaries, notes, topics, tags, comments, etc.).

  • A reliable and shared view of all client interactions.

  • Fewer errors and time saved on follow-up.

  • Better decision-making through cross-analysis of data.

In short: all essential data is accessible in both Modjo and Salesforce, improving efficiency and productivity.

2. How does the integration work?

Once activated, Modjo automatically synchronizes data whenever a call or meeting is imported.

A. Identification and logging of calls / meetings

  • Video conference meeting

    • Modjo analyzes your calendar (title, start time, end time) to identify the corresponding Event in Salesforce.

    • If the Event exists: it is enriched.

    • If not: a new Event is created.

  • Phone call

    • Modjo searches for the related Task Activity in Salesforce.

    • Same logic: enriches if it exists, or creates a new one if needed.

Data recorded in Salesforce includes:

  • Call link

  • Call duration

  • Topics

  • Summaries

  • Highlights

  • Notes

  • Modjo comments

  • Tags

  • Call provider


💡 Custom fields can also be populated using the CRM Filling feature (Accounts, Contacts, Opportunities, Leads).

B. Association with Salesforce standard objects

Modjo then links each activity to the relevant Salesforce objects:

  • Activity / Events

  • Lead

  • Contact

  • Account

  • Opportunity

Best practice : link the right objects (Task Activity or Event) before the call or meeting. This ensures Modjo retrieves the correct context and logs the activity properly.

For the full set of association rules, see the dedicated article.

3. Salesforce objects and fields: Permissions and required access

A. Details of required access

The table below outlines the required access to Salesforce objects for Modjo to leverage all features:

✅ = Mandatory
🟡 = Recommended
❌ = Not necessary

Objets Standards

Read (Consulter)

Edit (Modifier)

Create (Créer)

Comment

Contacts

🟡

Editing is recommended for the CRM Filling feature.

Activity

Leads

🟡

Editing is recommended for the CRM Filling feature.

Opportunities

🟡

Editing is recommended for the CRM Filling feature.

Accounts

🟡

Editing is recommended for the CRM Filling feature.

Notes

💡 Information from Salesforce is available in Modjo and vice versa, consolidating all relevant data in one place.

💡 To use custom CRM fields, ensure that Modjo has the necessary access rights. For more details, see our article on Modjo’s Salesforce integration.

B. Field Details by Object

Category

Imported Fields

Task Activity

Id: Unique task identifier

Type: Activity type
TaskSubtype: Task subtype
Description: Task description
Subject: Task subject
AccountId: Associated account ID
TaskWhoIds: Linked contact IDs
WhoId: Primary contact ID
WhatId: Related object ID
OwnerId: Task owner
ActivityDate: Activity date
Status: Task status
CallDurationInSeconds: Call duration in seconds
CallType: Call type
CallObject: Call object
aircall__CallId__c: Aircall call ID (if applicable)
VoiceCall__c: Amazon Cloud Voice call ID (if applicable)
CORE_FLEX_Audio_Record__c: Twilio call ID (if applicable)

Accounts

Id: Unique identifier of the account.
Name: Name of the account.

Opportunities (Deals)

Id: Unique identifier of the deal.
IsDeleted: Indicates if the deal has been deleted.
IsClosed: Indicates if the deal is closed. IsWon: Indicates if the deal has been won.
AccountId: Identifier of the associated account.
Name: Name of the deal.
OwnerId: Identifier of the deal's owner.
CreatedDate: Creation date of the deal.
StageName: Current stage of the deal.
Amount: Expected deal amount.
CurrencyIsoCode: Currency used for the deal.
CloseDate: Expected closing date of the deal.
LeadSource: Lead source for the deal.
Probability: Success probability of the deal (percentage).
LastModifiedDate: Last modification date of the deal.
ForecastCategoryName: Forecast category of the deal.
NextSteps: Planned next steps for the deal.
Type: Type of deal (e.g., new business, upsell, etc.).

Opportunity Contact Roles

ContactId: Unique identifier of the contact.
OpportunityId: Unique identifier of the opportunity.
Role: Role of the contact in the opportunity.

Leads

Id: Unique identifier of the lead.
LastName: Last name of the lead.
FirstName: First name of the lead.
Name: Full name of the lead (first and last name).
Phone: Primary phone number of the lead.
MobilePhone: Mobile phone number of the lead.
Email: Email address of the lead.
IsConverted: Indicates if the lead has been converted into a contact or opportunity.
ConvertedContactId: Identifier of the contact created after lead conversion.
Status: Current status of the lead (e.g., New, Qualified).
Title: Title or position of the lead.

Contacts

Id: Unique identifier of the contact.
AccountId: Identifier of the associated account.
LastName: Last name of the contact.
FirstName: First name of the contact.
Name: Full name of the contact (first and last name).
Phone: Primary phone number of the contact.
MobilePhone: Mobile phone number of the contact.
Email: Email address of the contact.
Title: Title or position of the contact.

Did this answer your question?