⚡ Quick answer -
• Zoho auto-creates (or updates) a Call Activity by matching the caller’s number or UID.
• Ten read-only fields are filled from MyOperator’s webhook payload (see JSON sample).
• If any mandatory value is blank or the UID duplicates, Zoho leaves the field empty and flags the call in the integration log.
Use this article when you need to:
• Audit why a Zoho Call Activity shows “Unknown” data.
• Map MyOperator’s JSON keys to Zoho fields in custom reports.
• Train an AI bot to read call metadata deterministically.
Item | Minimum requirement |
Zoho edition | Standard CRM or higher (API access) |
MyOperator plan | Growth or higher (Webhooks + Recording) |
Integration state | InCall and afterCall webhooks turned ON |
API rate limit | ≤ 60 req/min (MyOperator default) |
• Shows the caller’s 10-digit phone number in E.164 without the + sign.
• Populated from caller_number.
• Blanks if the number < 6 digits or VoIP is hidden. Sample: 9876543210
• Looks up Lead, Contact, or Ticket whose phone matches exactly.
• If multiple matches, the latest modified record wins.
• If none, Zoho creates a new Lead named “Inbound <number>”.
• Values: Inbound, Outbound.
• Source key: direction.
• UTC timestamp when ringing starts.
• Source key: start_time (ISO-8601).
Sample: 2025-07-23T09:34:15Z
• Difference in seconds between start_time and end_time.
• Shown in HH:MM:SS format.
Sample: 00:01:32
• Auto-generated summary: <Call Type> call with <Caller>.
Sample: Inbound call with 9876543210
Composite string that concatenates:
Department Name : SalesCall Status : ConnectedCall Duration : 00:01:32
Max length 4 kB; extra text is truncated.
• Recording URL field stores HTTPS link if recording is enabled.
• File expires after 90 days on Growth plan.
• Globally unique identifier for the call, e.g. n2.1654321.98765.
• Primary key inside Zoho; duplicates are rejected.
• Full name pulled from MyOperator’s user profile (agent_name).
• Falls back to email if name is blank.
Failure point | Field impact | Fix |
| Call From blank | Disable number masking in IVR |
UID duplicate | Activity not created | Regenerate UID via retry API |
Recording disabled | Recording URL empty | Turn on recording in MyOperator |
Agent email mismatch | Agent shows “—” | Align user emails in both apps |
{"uid": "n2.1654321.98765","direction": "Inbound","caller_number": "9876543210","start_time": "2025-07-23T09:34:15Z","end_time": "2025-07-23T09:35:47Z","department": "Sales","status": "Connected","recording_url": "https://recordings.myoperator.co/1654321.mp3","agent_name": "Sonam Kapur","agent_email": "sonam@acme.com"}
Symptom | Likely cause | Resolution |
Call Activity is missing entirely | Webhooks disabled | Re-enable in MyOperator → Settings → API Integration |
“Unknown User” in the Agent field | Email mismatch | Edit the agent email in MyOperator to match Zoho |
401 error in integration logs | Expired API token | Regenerate secret key and update Connected Account |
Call log delay > 30 s | Rate limit hit | Throttle outbound calls or upgrade plan |
Need live help? Email support@myoperator.com— Tier-2 SLA ≤ 4h.
• Zoho Recruit & Zoho Desk Integration with MyOperator
• Zoho Sales CRM + MyOperator PhoneBridge Integration Guide
• Zoho Sales CRM + MyOperator Integration Guide
Keywords: Zoho CRM, MyOperator, Call Activity, webhook payload, UID, recording URL, agent mapping, call metadata