Batch 7.1: Fix Zoho Lead Payload Mapping #75
Labels
No Label
P0 Critical
P1 High
P2 Medium
P3 Low
accessibility
backend
bug
content
data-integrity
enhancement
frontend
infra
integration
owner
owner-input
performance
performance
phase-7
phase-8
security
seo
ui
ux
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Queue-North-Website#75
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Batch 7.1 — Fix Zoho Lead Payload Mapping
Phase: 7 — Zoho CRM Integration
Agent: Neo (backend)
Priority: P1 High — wrong field mapping means leads land in Zoho with bad data
Problem
Contact form field mapping to Zoho CRM Lead schema has several issues:
namefield maps entirely toLast_Name— should split intoFirst_Name/Last_NameLead_Sourcefield — every web lead should haveLead_Source: "Website"Service_Interestis not a standard Zoho field — silently ignored unless custom field existstriggerparameter — should explicitly control Zoho workflow automations$approvedflag — web leads should route through approval workflowTasks
nameintoFirst_Name/Last_Name(split on last space; single word →Last_Nameonly)Lead_Source: "Website"to every lead payloadService_Interestfield withDescriptionfield (append service interest to message)"trigger": ["workflow"]to enable workflow automations explicitly"$approved": falsefor web-submitted leads going through approval queueFiles to modify
server/index.js—forwardToZoho()payload constructionAcceptance criteria
ZOHO_ENABLED=false