Quick start
From the Teamspace where you want meetings to land, open Settings → Integrations → Modjo → Connect, paste your Modjo API key, then create a subscription to auto-import new Modjo calls as Recordings in this Teamspace. Modjo provides an API to retrieve call data (including transcripts and summaries), and supports webhooks if you want near–real-time updates.
Why integrate with Modjo?
Each source adds a new dimension of customer truth. Modjo contributes the sales / customer-conversation perspective (discovery, demos, negotiations) that complements meetings, support tickets, surveys, and reviews already in NEXT AI—building a richer customer-intelligence graph so teams prioritize the right work with evidence attached.
What gets imported
Object in NEXT AI: Recording (conversational) in the Teamspace where the integration is connected.
Included fields (when available from Modjo): title/subject, media, timestamps/duration, participants/attendees, transcript and summary, and a source link back to Modjo. Modjo’s API lets you retrieve call data plus transcripts & summaries for downstream analysis.
Capture note: Modjo’s recorder/bot automatically joins Google Meet or Microsoft Teams meetings your org records, which is why those calls appear in Modjo (and then in NEXT AI).
Connect Modjo
Generate a Modjo API key: In Modjo → Settings → Integrations → Connect → Create API key, then Copy the key. (Admin or Manager permissions required.)
Paste the key in NEXT AI: In the target Teamspace: Settings → Integrations → Modjo → Connect → paste API key → Save.
After connection, NEXT AI uses the Modjo API to fetch calls for this Teamspace.
Auto-import calls
Create a subscription that watches for new Modjo calls and imports each as a Recording in this Teamspace.
Polling/event options: NEXT AI can pull via the Modjo API and/or align with Modjo webhooks for push delivery of new-call events and summaries, keeping your feed fresh.
Backfill: seed a recent window if offered, then let the subscription keep you up to date.
Tips
Ensure Modjo captured the call: Modjo’s recorder must have joined the meeting for a call to exist in Modjo (and thus be importable).
Use summaries for triage: Modjo’s summaries are handy signals—cluster them in NEXT AI to spot themes faster.
Mind Modjo’s org settings: Some Modjo tenants configure minimum call duration/import rules; those settings affect which meetings are available to import.
Troubleshooting
401/403 on connect — Re-check the API key and that your Modjo user has permissions to create/use API keys (Admin/Manager).
No calls appearing — Confirm the subscription is active, Modjo actually captured the meeting (recorder joined), and the call meets your Modjo org’s import thresholds (e.g., minimum duration).
We need near-real-time — Set up Modjo webhooks so new-call events/summaries POST to NEXT AI for faster ingestion.
FAQ
Q: What exactly is created in NEXT AI from Modjo?
A Recording per new Modjo call—with media, participants/timestamps, and, when available, transcript and summary, plus a source link back to Modjo.
Q: How do we authenticate? Where do we find the key?
Generate an API key in Modjo (Settings → Integrations → Connect → Create API key → Copy), then paste it in NEXT AI during connection. (Requires Admin/Manager rights.)
Q: Can we make imports near real-time?
Yes. Use Modjo webhooks so NEXT AI gets push notifications when a call (or summary) is ready. We’ll still keep a source link for traceability.
Q: Which meetings does Modjo capture?
Modjo’s recorder bot joins supported meetings (e.g., Google Meet, Microsoft Teams) and records them under your configured rules; those calls then become available via API for import.