Troubleshooting

A submission isn't showing up in Zoho

Before assuming it failed, check the view filter. Zoho CRM defaults its contacts/leads list to My Contacts — records created by an API/Self Client connection sometimes land under All Contacts instead. Switch the filter at the top of the list view before concluding a submission didn't arrive.

If it genuinely isn't there, check the Connect Log (below) — it'll tell you whether Connect even attempted the push.

Confirming a submission actually sent

Open Connect Log (WordPress: submenu under OtterContact Connect; Joomla: under Components → OtterContact Connect). Every submission from a mapped form is recorded there with a status:

• Sent — delivered to the CRM successfully.
• Pending Retry — the CRM request failed transiently and Connect will retry automatically.
• Failed — retries were exhausted; check the entry's detail for the CRM's error message.

Filter by form, CRM, status, or date range to narrow down a specific submission.

Zoho connection fails with a 400 error

This almost always means Data Center doesn't match where your Zoho account actually lives. Zoho's accounts server is region-specific — a .in account's credentials are rejected outright by the .com accounts server, and vice versa. Confirm:

• The Zoho API Console URL you created the Self Client from matches your account's actual region (api-console.zoho.in, .eu, etc.).
• Data Center on the Connect settings screen is set to that same region.
• The Org ID was copied from a CRM session in that same region, not a different one.

See Connecting a CRM for the full setup steps.

HubSpot says the token is invalid

HubSpot only shows a Private App's access token once, at creation — there's no way to view it again later. If you've lost it, you don't need to recreate the whole private app: open the existing app under Settings → Integrations → Private Apps, and generate a new token from there, then paste the new token into the Connect settings screen.