HTTP Request Node Returns 'No Refresh Token' Error When Accessing Zoho People API

Below is some guidance on troubleshooting the “No refresh token” error when using the HTTP Request node with Zoho People:

What the Error Means

The error indicates that when n8n attempted to authenticate using your Zoho People OAuth2 credentials, it did not find a refresh token in the token object. A refresh token is required to renew an expired access token automatically.

Steps to Troubleshoot

1. Review OAuth2 Scopes:
   Make sure that the OAuth2 flow for your Zoho People credentials includes the appropriate scopes to request offline access. Some providers require you to explicitly request a refresh token by including a scope (often called “offline_access” or similar) during the authorization step. Check Zoho People’s API documentation for the exact scope names.

2. Re-authorize the Credential:
   If your original credential setup did not include the refresh token, you may need to reauthenticate. In n8n, open your Zoho People credentials, trigger the OAuth2 flow again, and verify that the consent page lists the required permissions (including offline access if applicable). This ensures that a refresh token is issued during the process.

3. Check Your Redirect URI and App Settings:
   Ensure that the callback URL (redirect URI) configured in your Zoho developer app settings matches the one provided by n8n. A mismatch here can sometimes lead to incomplete token responses.

4. Inspect the Credential Settings in n8n:
   Double-check that the Zoho People credential configuration inside n8n is complete. In some cases, even if the credential was initially set up, changes in scopes or API settings at the provider’s end (Zoho People) might require resetting the credential.

5. Consult Zoho People’s API Documentation:
   Zoho People (like other Zoho services) may have nuances in their OAuth2 implementation. Revisit their API documentation to ensure that you are following all steps required to obtain a refresh token.

Summary

The absence of a refresh token typically means that during the OAuth2 authorization process the refresh token wasn’t returned. This can occur if the initial setup did not request offline access or if the OAuth2 configuration isn’t completely aligned with Zoho People’s requirements.

By rechecking your OAuth2 scopes, reauthorizing the credential within n8n, and verifying the app’s redirect URI settings, you should be able to obtain a refresh token and resolve the error.

If after these steps the issue still persists, consider checking the n8n community forums or support channels for any recent updates or additional troubleshooting steps specific to Zoho People integrations.