Why do cross-app Deluge calls fail in Zoho Creator?

Most cross-app Deluge failures come from the connection, not the code. Common causes are a connection missing the right scopes, a connection created by a user who lost access, the wrong data centre domain, a renamed field or module in the target app, and limits on the target app's API. Check the full response, not only whether the call ran, to see the real error.

When Creator calls Zoho CRM, Books or another app, it uses a connection that holds an OAuth token with certain scopes. If the scope does not cover the action, such as update instead of read, the call fails. If the person who authorised the connection leaves or loses permission in the target app, calls start failing for everyone. Rebuild connections under an admin or service account to avoid this.

Data centre mismatches are common for companies outside the US. An invokeurl call to a .com address will fail for an organisation hosted in the EU, India or another region. Use the right domain for your data centre, or use built-in integration tasks where they exist, which handle this for you.

Then check the payload. A required field missing, a picklist value that does not match, a wrong date format, or an ID from another organisation will return an error that Deluge does not throw by default. Log the response with info statements, read the code and message, and add checks so the script handles failures instead of silently moving on.

Written by Flowpeak, a Zoho implementation partner. Zoho pricing and features change, so confirm current details on the official Zoho site. Free checklists | Ask us a question