Google Sheets Common Issues

Common questions, error codes, and troubleshooting solutions for the Google Sheets node in SMSPort.

1. `PERMISSION_DENIED (403 Forbidden)`

Problem

The node execution fails and routes immediately to the error branch with the message:
The caller does not have permission to access the requested spreadsheet.

Cause

The connected Google Account or Service Account has not been granted access to the specific spreadsheet document.

Solution

1. Open the spreadsheet in your browser.
2. Click the green Share button in the top right.
3. If using OAuth: Ensure the Google Account you authorized in SMSPort has access.
4. If using Service Account: Share the sheet with the service account email (e.g. xyz@project.iam.gserviceaccount.com) as Editor.

2. `HEADER_NOT_FOUND`

Problem

The lookup operation returns empty results even though the data is present in the spreadsheet.

Cause

• Row 1 does not contain clean header strings.
• Trailing spaces exist in the header cell (e.g. "Phone " with a trailing space instead of "Phone").
• The Key Column or Result Column property in the inspector has a typographical difference.

Solution

1. Check Row 1 in your Google Sheet. Remove any leading or trailing spaces from header labels.
2. Verify that column names in the node inspector match Row 1 letter-for-letter (case-sensitive).

3. `redirect_uri_mismatch` During OAuth

Problem

When connecting Google OAuth in SMSPort, Google returns an error page stating Error 400: redirect_uri_mismatch.

Cause

The callback URL in your Google Cloud OAuth Client credentials does not match the SMSPort production domain.

Solution

1. Copy the exact redirect URL shown in the SMSPort popup:
   https://smsport.in/api/v1/integrations/google/callback
2. Open Google Cloud Console > Credentials.
3. Select your Web Application OAuth client ID.
4. Under Authorized redirect URIs, paste the exact URL and click Save.

4. `RATE_LIMIT_EXCEEDED (429 Too Many Requests)`

Problem

Google returns code 429 during large marketing broadcasts or high-traffic hours.

Cause

Google Sheets API enforces a limit of 300 requests per minute per project.

Solution

1. For high-volume campaigns, use the built-in PostgreSQL Database / Data Lookup node rather than direct Google Sheets calls.
2. Add a Delay Node of 1-2 seconds between bulk row iterations.