Missing Zoho OAuth2 Client ID and Secret Fields in n8n Credentials

Below is some background information that might help:

• When setting up Zoho OAuth2 credentials in n8n, the documentation instructs you to copy the OAuth Callback URL from n8n and use that in your Zoho app. You also need to copy your Client ID and Client Secret from Zoho to be entered in your n8n credential.

• In recent versions of n8n the Zoho credential is built around a Cloud OAuth button. This design means that the Client ID and Client Secret fields might not be visible in the credential configuration panel. Instead, the OAuth flow (triggered by the “Connect my account” button) is meant to automatically use these details from the OAuth setup you fully configure on the Zoho side.

Here are a few steps you might consider to resolve the issue:

1. Verify Your Version:
   Ensure you’re running the latest version of n8n. Updates can sometimes change how credentials are rendered or managed.

2. Double-Check the Credential Type:
   Make sure you are creating a Zoho credential (and not a generic OAuth2 credential) as the built-in Zoho integration uses the Cloud OAuth implementation.

3. Review the OAuth2 Setup Instructions:
   Follow the setup steps exactly as documented:

   • Register a Zoho application.
   • Use the n8n OAuth Callback URL in the Zoho Authorized Redirect URIs.
   • Copy the Client ID and Client Secret from Zoho (if applicable).

4. Contact Support/Community:
   If you’ve verified that your setup is correct and your n8n version is up-to-date but still don’t see the fields, this might be a bug or a design change. It could help to report this issue in the n8n community forum or consult with support. Other users may have encountered similar behavior and could offer workarounds.

In summary, due to the way OAuth2 credentials are implemented for Zoho in n8n via the Cloud OAuth button, you might not see separate Client ID and Client Secret input fields. Instead, the connection is established by clicking “Connect my account” and letting the OAuth flow handle the underlying parameters. Make sure to review that your Zoho OAuth app is configured properly with the correct callback URL and that you’re using the latest version of n8n.

Hope this helps clarify the issue and point you toward a resolution!