Skip to main content

Manually import a call/meeting into Modjo

Easily add your calls or meetings into Modjo

Updated this week

Easily add your calls or meetings into Modjo, either individually via the interface or in bulk via the Modjo API.

Introduction

Manual import allows you to add calls or meetings that were not automatically imported into Modjo. This feature can be particularly useful in scenarios like:

  • Recording a training session

  • Importing a meeting you recorded but did not organize

  • Reviewing a recorded call before importing it into Modjo

  • Uploading calls made through a telephony system not integrated with Modjo

  • Migrating a large volume of historical recordings


Method 1: Individual import via Modjo interface

Step 1: Download your recording

Rules for displaying the "Import a Call" option

  • Administrator with or without a license:

    • The "Import a Call" option is always displayed. ✅

  • Manager or user with a license:

    • The "Import a Call" option is displayed. ✅

  • Manager or User without a License:

    • The "Import a Call" option is hidden. ❌

💡 Before manually importing a call, ensure the call meets the minimum duration criteria set by your organization’s Account Manager or administrator.

e.g.: If the minimum duration is set to 2 minutes, calls shorter than this cannot be imported manually.

For more details or to update this setting, please contact your Account Manager or admin.

  • Retrieve the recording from your provider's cloud (e.g., Zoom, Google Meet).

  • Ensure the file is in a compatible format: wav, mp3, m4a or mp4.

  • Go to Home > Click on the three dots located at the top-right corner of the screen > Select Import call.

Step 2: Import your call or meeting

🚨Prerequisites:

  • Active recording license required: You need to have an active Modjo recording license.

  • Mandatory host: Provide the name of a host, such as an email address or a phone number.

  • Mandatory client contact: Please provide a client contact, such as an email address or phone number. If the contact does not appear in the dropdown list, you can still add it manually. It will then be linked to the call in Modjo.

    Please note, it will not be added to your CRM if it hasn't been created beforehand, but you can add it to your CRM later.

  • Do not close the page: Wait until the message "Uploading call" disappears before closing the page to ensure the file uploads successfully.

💡 Good to know:

Import: This is the step where Modjo retrieves the call (audio or video), generates a transcription, associates relevant data, and makes it accessible to the client on Modjo.

Upload: This refers to the action of adding a recording (call or video conference) to Modjo's server.

Troubleshooting

A. The file does not upload

Verify that the file is in the correct format: wav, mp3, m4a or mp4.

B. The file does not appear in Modjo after import

Refresh the Modjo page and check your internet connection.

C. If the following error message appears: "contacts contain not a valid id, email, or crmContact".

It means you must enter a valid contact (email address or phone number) in the input field.


Method 2: Bulk import via Modjo API

To import multiple calls simultaneously or automate your imports, use the Modjo API. This method is ideal for migrating historical recordings or integrating Modjo into your technical workflows.

⚙️ Important: This method requires technical skills. We recommend performing this import in collaboration with a member of your technical team or your IT department if needed.

Prerequisites

  • Access to your data: Recording files (mp3, wav, mp4) or recording URL + associated metadata (date, user email + contact email/phone number)

  • Access to your Modjo workspace

  • Basic knowledge of REST APIs

How does API upload work?

Uploading a call to Modjo takes 2 steps, with two possible use cases:

Use Case 1: Providing a Recording URL

  • Send a POST request to the endpoint with the call metadata, including the recording URL (recordingUrl parameter)

  • You will receive an acknowledgement response with {success: true}

  • Modjo will download the recording from the provided URL within 30 minutes, typically within 5 minutes

Use Case 2: Receiving a Signed URL for Upload

  • Send a POST request to the endpoint with the call metadata (without recordingUrl)

  • You will receive a signed URL to upload the recording file

  • Use this URL to upload your recording file with a PUT request

💡 In both cases, the metadata sent in the first request will be automatically attached to the recording in Modjo.

Steps to follow

  1. Create an API key: Generate an API key from your Modjo workspace (Settings > Integrations > API)

  2. Write a sending script: Develop a script that sends recordings (file or URL) and metadata to the Modjo API

🔗 For complete details (request structure, code examples, error handling), please refer to our technical documentation: Modjo API Documentation - Upload Call

Key API parameters

Endpoint: POST https://api.modjo.ai/v1/calls/upload

Required headers:

  • Authorization: Bearer YOUR_API_KEY

  • Content-Type: multipart/form-data (if sending file)

  • Content-Type: application/json (if sending URL)

Required parameters

  • users: List of Modjo user identifiers (array, only one user for now)

  • contacts: List of contact identifiers to associate with the call (integer, string, or CRM object)

  • date: Call date and time in ISO 8601 format

  • fileExtension: File extension (wav, mp3, mpeg, m4a, mp4, webm)

  • tags: Array of tags associated with the call (non-empty)

Optional parameters

  • name: Call title

  • duration: Duration in seconds (minimum 120s by default)

  • recordingUrl: Recording file URL (alternative to direct upload)

  • account: CRM account identifier to associate

  • deal: CRM opportunity identifier to associate

  • direction: Call direction (inbound or outbound, default inbound)

  • provider: Call provider name (default manual)

Complexity and estimated time

Complexity: Low

Estimated time: 1-2 days (experimentation + testing + data migration)

💡 Recommendation: Test first with 2-3 calls before migrating all your recording

Did this answer your question?